Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-6183

Skip bad workers when re-launching executors

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Incomplete
    • None
    • None
    • Deploy

    Description

      In standalone cluster, when an executor launch fails, the master should avoid re-launching it on the same worker.
      According to the current scheduling logic, the failed executor will be highly possible re-launched on the same worker, and finally cause the application removed from the master.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SPARK-1499 Workers continuously produce failing executors

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. SPARK-4609 Job can not finish if there is one bad slave in clusters

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. SPARK-6353 Handling fatal errors of executors and decommission datanodes

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. SPARK-4609 Job can not finish if there is one bad slave in clusters

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

          Pull request #4909 [Github] Pull Request #4909 (zhpengg)

          Activity

            People

              Unassigned Unassigned
              zhpengg Zhen Peng
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: