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

ApplicationState.MAX_NUM_RETRY should be configurable

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 1.0.0
    • 1.6.3, 2.0.1, 2.1.0
    • Spark Core
    • None

    Description

      ApplicationState.MAX_NUM_RETRY, controlling the number of times standalone Executors can exit unsuccessfully before Master will remove the Application that the Executors are trying to run, is currently hard-coded to 10. There's no reason why this should be a single, fixed value for all standalone clusters (e.g., it should probably scale with the number of Executors), so it should be SparkConf-able.

      Attachments

        Issue Links

          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. SPARK-16956 Make ApplicationState.MAX_NUM_RETRY configurable

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

          Bug - A problem which impairs or prevents the functions of the product. SPARK-2425 Standalone Master is too aggressive in removing Applications

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

          Pull request #3548 [Github] Pull Request #3548 (JoshRosen)

          Activity

            People

              joshrosen Josh Rosen
              markhamstra Mark Hamstra
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: