Uploaded image for project: 'REEF (Retired)'
  1. REEF (Retired)
  2. REEF-1715

Remove System.exit() at the end of the REEF launcher

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • REEF Driver, REEF Evaluator, REEF-Common
    • None

    Description

      After all recent cleanup efforts in REEF, we no longer need to use System.exit(0) to forcefully quit the JVM at the end of the REEF job. We can safely remove that call.

      We also don't have to dump threads at the end of the REEFEnvironment life cycle (this is redundant in the Unmanaged AM / REEF-as-a-library mode) - REEFLauncher is a better place to log such information because this is where we actually exit the JVM.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. REEF-2014 Azure Batch REEF .NET Driver is not able to exit when using REEFEnvironment to launch

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. REEF-1756 Make sure there's System.exit() at the end of each REEFEnvironment process; add TODO comment to each call

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Resolved

          Activity

            People

              motus Sergiy Matusevych
              motus Sergiy Matusevych
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified