Github user BrainLogic commented on the issue:
https://github.com/apache/flink/pull/3035
I caught yours idea and together with the argument which I mentioned above
- users will not extensively use 8 version of kafka connector, I agree with
this proposal.
Let me finish this jira
Github user BrainLogic commented on the issue:
https://github.com/apache/flink/pull/3035
Distributed systems and multithreading environments make us think in term
of logical clock, like Lamport clock, step by step:
Thread1 - fetcher is running `running = true`
Thread2 performs
Github user BrainLogic commented on the issue:
https://github.com/apache/flink/pull/3035
Thanks for help and explanation.
But in this approach an unlikely bug will be still occurred:
`zkHandler.prepareAndCommitOffsets(offsets);` throws important exception
when running is true
GitHub user BrainLogic opened a pull request:
https://github.com/apache/flink/pull/3035
[ FLINK-4905] Kafka test instability IllegalStateException: Client is not
started
Root cause of the issue:
`notifyCheckpointComplete` can occur during the cancellation or
`runFetchLoop
