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] increase checkpoint timeout #5722
Comments
This should not be a bug, just increase the checkpoint timeout according to the log prompts. I also encountered this issue, and after increasing the timeout, the problem was resolved |
i tried, but this solution is not work 4 me :( |
i met this in 2.3.4 version , like: |
Version 2.3.4 has not been released yet, and the config may change at any time. The company only allows stable versions, so...... I have to wait for the next stable version to be released or fixed with patches |
Avoid reading large files or using scroll queries in Elasticsearch, as the pollNext method tends to hold the checkpointLock indefinitely, leading to checkpoint timeout.
Avoid reading large files or using scroll queries in Elasticsearch, as the pollNext method tends to hold the checkpointLock indefinitely, leading to checkpoint timeout.
Avoid reading large files or using scroll queries in Elasticsearch, as the pollNext method tends to hold the checkpointLock indefinitely, leading to checkpoint timeout.
Avoid reading large files or using scroll queries in Elasticsearch, as the pollNext method tends to hold the checkpointLock indefinitely, leading to checkpoint timeout.
Avoid reading large files or using scroll queries in Elasticsearch, as the pollNext method tends to hold the checkpointLock indefinitely, leading to checkpoint timeout.
hi @mengyueyue.How much data do you synchronize? I have a table whose size is 7.4g and timeout has been increased. But I still get this error. |
my data size is 4.7g and i set int max value for them |
Avoid reading large files or using scroll queries in Elasticsearch, as the pollNext method tends to hold the checkpointLock indefinitely, leading to checkpoint timeout.
thx for reply |
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. |
Search before asking
What happened
When I use batch mode to synchronize data, I always prompt for checkpoint timeout
SeaTunnel Version
2.3.3
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
No response
Java or Scala Version
JDK11
Screenshots
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: