[
https://issues.apache.org/jira/browse/FLINK-38499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song closed FLINK-38499.
--------------------------------
Fix Version/s: 2.0.1
2.2.0
2.1.1
Resolution: Fixed
- master (2.2): 7b783591192a942c7bac8a7b20e4e75e5684a87c
- release-2.1: 4a12bac87b24163a03f89b73588b6d05deb2c5b7
- release-2.0: 2a5ad332ca9928b6fcb98fbfe57ff9099a0f72d3
> Limit max sleep time in Curator for Zookeeper HA
> ------------------------------------------------
>
> Key: FLINK-38499
> URL: https://issues.apache.org/jira/browse/FLINK-38499
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 2.0.1, 2.2.0, 2.1.2
> Reporter: Mingliang Liu
> Assignee: Mingliang Liu
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.1, 2.2.0, 2.1.1
>
>
> Currently, the Curator framework used by ZK based HA is using the exponential
> backoff retry policy. However, the max sleep time is unbounded. That could
> cause unbounded sleep time when the retryCount is large. When that happens,
> recovery from ZK issues may be unreasonably slow.
> In my day job, we have a critical patch that limits the max sleep time after
> seeing multiple ZK issues in the past. In other Apache projects, the
> {{BoundedExponentialBackoffRetry}} is widely used, such as fluss, druid,
> hudi, bookeeper, phoeniex, hbase...to name a few.
> This Jira proposes to limit the max sleep time by leveraging
> {{{}BoundedExponentialBackoffRetry{}}}, with a 60s default value for
> starters. Users can change this via a new config option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
