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

FSNamesystemLock metrics can be inaccurate due to millisecond precision

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.7.4
    • Fix Version/s: 2.9.0, 2.7.4, 3.0.0-alpha4, 2.8.2
    • Component/s: hdfs
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Currently the FSNamesystemLock metrics created in HDFS-10872 track the lock hold time using Timer.monotonicNow(), which has millisecond-level precision. However, many of these operations hold the lock for less than a millisecond, making these metrics inaccurate. We should instead use System.nanoTime() for higher accuracy.

        Attachments

        1. HDFS-11615.001.patch
          15 kB
          Erik Krogen
        2. HDFS-11615.000.patch
          9 kB
          Erik Krogen

        Issue Links

          Activity

            People

            • Assignee:
              xkrogen Erik Krogen
              Reporter:
              xkrogen Erik Krogen

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment