Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-10437

Destroy yarn service if any YarnException occurs during submitApp

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 3.4.0, 3.3.1
    • yarn-native-services
    • None
    • Reviewed

    Description

      If a user submits a yarn service with configuration such that it causes an exception during application submission, the files related to the service are not cleared from hdfs automatically. Ideally the files stored to hdfs cannot be used in future to start or stop the service as the configuration itself is invalid. So, we should destroy the service and remove the residual files in hdfs, if any YarnException is thrown.

      For example if the user submits a service with configuring with "memory" more than the maximum resource, the service fails but the files in hdfs are not cleared. But these files should be cleared.

      Attachments

        1. YARN-10437.001.patch
          2 kB
          D M Murali Krishna Reddy
        2. YARN-10437.002.patch
          5 kB
          D M Murali Krishna Reddy

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dmmkr D M Murali Krishna Reddy
            dmmkr D M Murali Krishna Reddy
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment