Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-4299

Show loss of job manager in Client



    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0, 1.2.0
    • Component/s: Command Line Client
    • Labels:


      If the client looses the connection to a job manager and the job recovers from this, the client will only print the job status as RUNNING again. It is hard to actually notice that something went wrong and a job manager was lost.

      08/01/2016 14:35:43     Flat Map -> Sink: Unnamed(8/8) switched to RUNNING
      08/01/2016 14:35:43     Source: Custom Source(6/8) switched to RUNNING
      <------ EVERYTHING'S RUNNING ------>
      08/01/2016 14:40:40     Job execution switched to status RUNNING <--- JOB MANAGER FAIL OVER
      08/01/2016 14:40:40     Source: Custom Source(1/8) switched to SCHEDULED
      08/01/2016 14:40:40     Source: Custom Source(1/8) switched to DEPLOYING
      08/01/2016 14:40:40     Source: Custom Source(2/8) switched to SCHEDULED

      After 14:35:43 everything is running and the client does not print any execution state updates. When the job manager fails, the job will be recovered and enter the running state again eventually (at 14:40:40), but the user might never notice this.

      I would like to improve on this by printing some messages about the state of the job manager connection. For example, between 14:35:43 and 14:40:40 it might say that the job manager connection was lost, a new one established, etc.


          Issue Links



              • Assignee:
                mxm Maximilian Michels
                uce Ufuk Celebi
              • Votes:
                0 Vote for this issue
                3 Start watching this issue


                • Created: