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

DataXceiver#run() should not log exceptions caused by InvalidToken exception as an error

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.0.4, 3.3.0, 3.2.1, 3.1.3
    • Component/s: hdfs
    • Labels:
      None

      Description

      HDFS-10760 changed the log level from error to trace in DataXceiver#run() if the exception was an InvalidToken exception. I think it would be beneficial to log on trace level if the exception's cause was InvalidException. Like in the following case:

      DataXceiver error processing unknown operation 
      src: xxx dst: xxx
      javax.security.sasl.SaslException: DIGEST-MD5: IO error acquiring password [Caused by org.apache.hadoop.security.token.SecretManager$InvalidToken: Block token with block_token_identifier
      (expiryDate=1547593336220, keyId=-1735471718, userId=hbase, blockPoolId=BP-xxx, blockId=1245599303, access modes=[READ]) is expired.]
      

        Attachments

        1. HDFS-14231.001.patch
          1 kB
          Kitti Nanasi

          Issue Links

            Activity

              People

              • Assignee:
                knanasi Kitti Nanasi
                Reporter:
                knanasi Kitti Nanasi
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: