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

Add Timestamp for longest FSN write/read lock held log

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.3.0
    • None
    • None
    • Reviewed

    Description

      HDFS-13946 improved the log for longest read/write lock held time, it's very useful improvement.

      In some condition, we need to locate the detailed call information(user, ip, path, etc.) for longest lock holder, but the default throttle interval(10s) is too long to find the corresponding audit log. I think we should add the timestamp for the longestWriteLockHeldStackTrace

      Attachments

        1. HDFS-14775.001.patch
          9 kB
          Chen Zhang
        2. HDFS-14775.002.patch
          10 kB
          Chen Zhang
        3. HDFS-14775.003.patch
          10 kB
          Chen Zhang
        4. HDFS-14775.004.patch
          9 kB
          Chen Zhang
        5. HDFS-14775.005.patch
          9 kB
          Chen Zhang

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. HDFS-15215 The Timestamp for longest write/read lock held log is wrong

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. HDFS-15217 Add more information to longest write/read lock held log

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              zhangchen Chen Zhang
              zhangchen Chen Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: