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

Do not require a storage ID or target storage IDs when writing a block

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 3.0.0-alpha4
    • 3.0.0-alpha4
    • None
    • None
    • Hide
      Hadoop 2.x clients do not pass the storage ID or target storage IDs when writing a block. For backwards compatibility, the DataNode will not require the presence of these fields. This means older clients are unable to write to a particular storage as chosen by the NameNode (e.g. HDFS-9806).
      Show
      Hadoop 2.x clients do not pass the storage ID or target storage IDs when writing a block. For backwards compatibility, the DataNode will not require the presence of these fields. This means older clients are unable to write to a particular storage as chosen by the NameNode (e.g. HDFS-9806 ).

    Description

      Seems like HDFS-9807 broke backwards compatibility with Hadoop 2.x clients. When talking to a 3.0.0-alpha4 DN with security on:

      2017-06-06 23:27:22,568 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Block token verification failed: op=WRITE_BLOCK, remoteAddress=/172.28.208.200:53900, message=Block token with StorageIDs [DS-c0f24154-a39b-4941-93cd-5b8323067ba2] not valid for access with StorageIDs []
      

      Attachments

        1. HDFS-11956.001.patch
          14 kB
          Ewan Higgs
        2. HDFS-11956.002.patch
          16 kB
          Ewan Higgs
        3. HDFS-11956.003.patch
          17 kB
          Ewan Higgs
        4. HDFS-11956.004.patch
          4 kB
          Ewan Higgs

        Issue Links

          Activity

            People

              ehiggs Ewan Higgs
              andrew.wang Andrew Wang
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: