Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-4911 Non-disruptive JobManager Failures via Reconciliation
  3. FLINK-5861

TaskManager's components support updating JobManagerConnection

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • Runtime / Coordination
    • None

    Description

      Some components in TaskManager, such as TaskManagerActions, CheckpointResponder, ResultPartitionConsumableNotifier, PartitionProducerStateChecker, need to support updating JobManagerConnection. So when JobManager fails and recovers, the tasks who keep old JobManagerConnection can be notified to update JobManagerConnection. The tasks can continue doing their jobs without failure.

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue FLINK-5862 When JobManager fails, TaskManagers do not cancel tasks, but attempt to reconnect to the JobManager, and report states of tasks deployed in

          • Major - Major loss of function.
          • Closed
          links to

          Web Link GitHub Pull Request #3395

          Activity

            People

              SleePy Biao Liu
              SleePy Biao Liu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: