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

NameNode implementation of ClientProtocol.truncate(..) is not idempotent

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.7.0
    • Component/s: namenode
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      If dfsclient drops the first response of a truncate RPC call, the retry by retry cache will fail with "DFSClient ... is already the current lease holder". The truncate RPC is annotated as @Idempotent in ClientProtocol but the NameNode implementation is not.

        Attachments

        1. h7926_20150313b.patch
          3 kB
          Tsz Wo Nicholas Sze
        2. h7926_20150313.patch
          2 kB
          Tsz Wo Nicholas Sze

          Activity

            People

            • Assignee:
              szetszwo Tsz Wo Nicholas Sze
              Reporter:
              szetszwo Tsz Wo Nicholas Sze
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: