john-karp opened a new pull request #17785:
URL: https://github.com/apache/flink/pull/17785
## What is the purpose of the change
High-volume Kinesis consumers can sporadically get Connect errors when
connecting to the Kinesis endpoint.
Current behavior is to consider this a fatal error, causing Flink to roll
back to previous checkpoint. However retries will typically lead to success, so
this patch causes connect errors to be considered recoverable.
## Brief change log
- Make ConnectTimeoutException recoverable
- Unit test for above
## Verifying this change
- New unit test
- Applying this patch has allowed one of our Flink jobs to run continuously,
instead of failing several times per day.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
