Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Kafka source STREAMING] Kafka source connector doesn't capture new data from topic #8107

Open
2 of 3 tasks
maerman13 opened this issue Nov 22, 2024 · 6 comments
Open
2 of 3 tasks
Labels

Comments

@maerman13
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

SeaTunnel 2.3.8 + Apache Flink Flink engine + Streaming mode.
Kafka source connector doesn't capture new data from topic, but there are no exception while execution.
New data appears in topic, but doesn't transfer to Redis.
In Batch mode everything works, but we need streaming mode with flink.

SeaTunnel Version

SeaTunnel 2.3.8

SeaTunnel Config

# Defining the runtime environment
env {
  parallelism = 1
  job.mode = "STREAMING"
  job.name=SeaTunnel_Job_Kafka_Redis_Streaming
  shade.identifier = "base64"
  execution.checkpoint.interval = 60000
}

source {
  Kafka {
    schema = {
      fields {
        age = "int"
      }
    }
    format = text
    field_delimiter = "#"
    topic = "registrations"
    bootstrap.servers = "_"
    commit_on_checkpoint=false
    poll.timeout = 1000
    start_mode = "earliest"
    kafka.config = {
      auto.offset.reset = "earliest"
      enable.auto.commit = "false"
      client.id = client_1
    }

  }  
}

sink {
  Redis {
    host = "_"
    port = 6379
    key = age
    data_type = hash
    auth = "_"
    batch_size = 1
  }
}

Running Command

slatunnel flink 15 command

Error Exception

No errors, task work without error, but there no new data

Zeta or Flink or Spark Version

Apache Flink

Java or Scala Version

No response

Screenshots

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@maerman13 maerman13 added the bug label Nov 22, 2024
@AceGain
Copy link

AceGain commented Nov 26, 2024

I have encountered the same problem, have you solved it?

@sunxiaojian
Copy link
Contributor

give more log info

@eee27
Copy link

eee27 commented Nov 28, 2024

same problem,but i use rocketmq->starrocks and mongo-cdc->starrocks,only few table have this problem

@AceGain
Copy link

AceGain commented Nov 28, 2024

give more log info

This pr seems to have been fixed in 7871.

@sunxiaojian
Copy link
Contributor

give more log info

This pr seems to have been fixed in 7871.

@AceGain @maerman13 ok , If it has been resolved, please close it

@sunxiaojian
Copy link
Contributor

same problem,but i use rocketmq->starrocks and mongo-cdc->starrocks,only few table have this problem

@eee27 Open an new issue, describe the problem and configuration clearly, preferably with logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants