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

Failure of shutdown lead to restart of (connected) pipeline

    XMLWordPrintableJSON

Details

    Description

      This bug happened in combination with https://issues.apache.org/jira/browse/FLINK-21028 .

      When I wanted to stop a job via CLI "flink stop..." with disjoint job graph (independent pipelines in the graph), one task wan't able to stop properly (Reported in mentioned bug). This lead to restarting the job. I think, this is a wrong behavior in general and a separated bug:

      If any crash occurs on (trying) to stop a job, Flink shouldn't try to restart but continue stopping the job.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. FLINK-21030 Broken job restart for job with disjoint graph

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. FLINK-21028 Streaming application didn't stop properly

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              Unassigned Unassigned
              TheoD Theo Diefenthal
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: