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

Disabling atime may fail clients like distCp

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 3.0.0-alpha1
    • Component/s: None
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      When atime is disabled, setTimes() throws an exception if the passed-in atime is not -1. But since atime is not -1, distCp fails when it tries to set the mtime and atime.

      There are several options:

      1) make distCp check for 0 atime and call setTimes() with -1. I am not very enthusiastic about it.
      2) make NN also accept 0 atime in addition to -1, when the atime support is disabled.
      3) support setting mtime & atime regardless of the atime support. The main reason why atime is disabled is to avoid edit logging/syncing during getBlockLocations() read calls. Explicit setting can be allowed.

        Attachments

        1. HDFS-9208.v2.patch
          3 kB
          Kihwal Lee
        2. HDFS-9208.patch
          3 kB
          Kihwal Lee

          Issue Links

            Activity

              People

              • Assignee:
                kihwal Kihwal Lee
                Reporter:
                kihwal Kihwal Lee
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: