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

Fix error message of tokens' activation delay configuration

VotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 2.6.0
    • 2.7.0
    • None
    • None
    • Reviewed

    Description

      this.rollingInterval = conf.getLong(
               YarnConfiguration.RM_CONTAINER_TOKEN_MASTER_KEY_ROLLING_INTERVAL_SECS,
              YarnConfiguration.DEFAULT_RM_CONTAINER_TOKEN_MASTER_KEY_ROLLING_INTERVAL_SECS) * 1000;
      ...
      this.activationDelay =
              (long) (conf.getLong(YarnConfiguration.RM_NM_EXPIRY_INTERVAL_MS,
                  YarnConfiguration.DEFAULT_RM_NM_EXPIRY_INTERVAL_MS) * 1.5);
      ...
      if (rollingInterval <= activationDelay * 2) {
            throw new IllegalArgumentException(
                YarnConfiguration.RM_CONTAINER_TOKEN_MASTER_KEY_ROLLING_INTERVAL_SECS
                    + " should be more than 2 X "
                    + YarnConfiguration.RM_CONTAINER_TOKEN_MASTER_KEY_ROLLING_INTERVAL_SECS);
          }
      

      The error msg should be

      YarnConfiguration.RM_CONTAINER_TOKEN_MASTER_KEY_ROLLING_INTERVAL_SECS
                    + " should be more than 3 X "
                    + YarnConfiguration.RM_NM_EXPIRY_INTERVAL_MS);
      

      Also It's 3 X instead of 2 X, since it's multiplied by 1.5.
      There are few other places having same issue.

      Attachments

        1. YARN-3058.001.patch
          4 kB
          Yi Liu

        Issue Links

        Activity

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

          People

            hitliuyi Yi Liu
            hitliuyi Yi Liu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment