flink
flink copied to clipboard
[BP-2.0][FLINK-37747][runtime] Use old subtask count for restored committable…
Backport of https://github.com/apache/flink/pull/26518
CI report:
- dfa2efba36301f63ac4932e5cb39b67da3b7439d Azure: SUCCESS
Bot commands
The @flinkbot bot supports the following commands:@flinkbot run azurere-run the last Azure build
@bjlovegithub please could you prefix the PR title with [BP-2.0] similar to PR 26561 - it is helpful to easily identify the backports.
@davidradl yep, updated the PR title
This PR is being marked as stale since it has not had any activity in the last 90 days. If you would like to keep this PR alive, please leave a comment asking for a review. If the PR has merge conflicts, update it with the latest from the base branch.
If you are having difficulty finding a reviewer, please reach out to the community, contact details can be found here: https://flink.apache.org/what-is-flink/community/
If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.
Is this issue still present on 1.20, 1.19? I was reading it here and it seems like it was never backported https://issues.apache.org/jira/si/jira.issueviews:issue-html/FLINK-37747/FLINK-37747.html
We are experiencing this on version 1.20.2, basically as soon as we scale our job the Flink Application stops working and our delta tables don't get updated.
This issue here is that we cannot use Flink 2 yet, given that Flink Delta does not support Flink 2.
Are there any plans of backporting this fix for the earlier versions?
@bjlovegithub Are you still want to contribute the change? I can help with the review and merge but can you first rebase and fix the conflict?
Thanks @fapaul I fixed the conflict.
The branch is still shown as having conflicts. Can you double-check that?
hey @fapaul I cannot find conflict file.. can you point out which file?
Ok let me check what's going on I only see
@bjlovegithub I just tried rebasing this PR with the most recent 2.0 branch and it has conflicts. Can you please make sure you are rebasing with the origin of release-2.0, or make sure that your local release-2.0 is in sync with upstream before starting the rebase?
@fapaul ah just realised my forked 2.0 release branch is out of sync.. I rebased from 2.0 release branch from flink repo. Should be OK now. Waiting for the build bot to finish.