[FLINK-13223] Set jobmanager.execution.failover-strategy to region in default flink-conf.yaml - ASF JIRA

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Closed
Priority: Blocker
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 1.9.0
Component/s: Runtime / Coordination
Labels:
- pull-request-available

Release Note:

Hide
Flink will now by default use the "region" failover strategy. Flink will now attempt to only restart tasks that are connected to the failed task through a pipelined connection.

Users who were not using a restart strategy or have already configured a failover strategy should not be affected.

Streaming users who were not using a failover strategy may be affected if their jobs are embarrassingly parallel or contain multiple independent jobs. In this case, only the failed parallel pipeline or affected jobs will be restarted.

Batch users may be affected if their job contains blocking exchanges (usually happens for shuffles) or the ExecutionMode was set to BATCH or BATCH_FORCED via the ExecutionConfig.

Overall users should see an improvement in performance.

Show
Flink will now by default use the "region" failover strategy. Flink will now attempt to only restart tasks that are connected to the failed task through a pipelined connection. Users who were not using a restart strategy or have already configured a failover strategy should not be affected. Streaming users who were not using a failover strategy may be affected if their jobs are embarrassingly parallel or contain multiple independent jobs. In this case, only the failed parallel pipeline or affected jobs will be restarted. Batch users may be affected if their job contains blocking exchanges (usually happens for shuffles) or the ExecutionMode was set to BATCH or BATCH_FORCED via the ExecutionConfig. Overall users should see an improvement in performance.