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] [CheckPoint] checkpoint ineffective #6874

Closed
2 of 3 tasks
15767714253 opened this issue May 20, 2024 · 4 comments
Closed
2 of 3 tasks

[Bug] [CheckPoint] checkpoint ineffective #6874

15767714253 opened this issue May 20, 2024 · 4 comments

Comments

@15767714253
Copy link

Search before asking

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

What happened

image
image
image

SeaTunnel Version

2.3.5

SeaTunnel Config

env {
  execution.parallelism = 2
  job.mode = "BATCH"
  checkpoint.interval = 2000
  read_limit.rows_per_second=1
  job.name = cell-Job
}

source {

    InfluxDB {
        result_table_name = "test"
        url = "http://localhost:8086"
        sql = "select number from test1"
        database = "mydb"
        username = "admin"
        password = "123456"
        upper_bound = 10
        lower_bound = 1
        partition_num = 10
        split_column = "number"
        query_timeout_sec = 60
        connect_timeout_ms = 150000
        chunk_size = 1
        chunk_read = true
        schema {
                fields {
                         number = INT
                }
        }
    }

}


sink {
  Console {
          source_table_name = "test"
        }

}

Running Command

./start-seatunnel-flink-15-connector-v2.sh --config ../jobs/job.txt

Error Exception

**BATCH    checkpoint ineffective**

Zeta or Flink or Spark Version

No response

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

@liunaijie
Copy link
Contributor

using streaming mode

@15767714253
Copy link
Author

using streaming mode
this source support batch mode only

Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Jun 21, 2024
Copy link

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

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

No branches or pull requests

2 participants