Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-14630

Configuration.getTimeDurationHelper() should not log time unit warning in info log.

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 3.1.1
    • 3.3.0, 3.2.3
    • hdfs
    • None

    Description

      To solve HDFS-12920 issue we configured "dfs.client.datanode-restart.timeout" without time unit. No log file is full of

      2019-06-22 20:13:14,605 | INFO  | pool-12-thread-1 | No unit for dfs.client.datanode-restart.timeout(30) assuming SECONDS org.apache.hadoop.conf.Configuration.logDeprecation(Configuration.java:1409)

      No need to log this, just give the behavior in property description.

      Attachments

        Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. HDFS-12920 HDFS default value change (with adding time unit) breaks old version MR tarball work with Hadoop 3.x

        • Critical - Crashes, loss of data, severe memory leak.
        • Resolved

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

          People

            hemanthboyina Hemanth Boyina Assign to me
            surendralilhore Surendra Singh Lilhore
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment