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

WebHdfs returns misleading error code and logs nothing if trying to create a file with no DNs in cluster

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.3.0
    • 2.4.0
    • hdfs-client
    • None
    • Reviewed

    Description

      When trying to access hdfs via webhdfs, and when datanode is dead, user will see an exception below without any clue that it's caused by dead datanode:

      $ curl -i -X PUT ".../webhdfs/v1/t1?op=CREATE&user.name=<userName>&overwrite=false"

      ...
      {"RemoteException":{"exception":"IllegalArgumentException","javaClassName":"java.lang.IllegalArgumentException","message":"n must be positive"}}

      Need to fix the report to give user hint about dead datanode.

      Attachments

        1. HDFS-5939.001.patch
          7 kB
          Yongjun Zhang
        2. HDFS-5939.002.patch
          8 kB
          Yongjun Zhang
        3. HDFS-5939.003.patch
          5 kB
          Yongjun Zhang
        4. HDFS-5939.004.patch
          5 kB
          Yongjun Zhang
        5. HDFS-5939.005.patch
          5 kB
          Yongjun Zhang
        6. HDFS-5939.006.patch
          4 kB
          Yongjun Zhang
        7. HDFS-5939.007.patch
          4 kB
          Yongjun Zhang

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            yzhangal Yongjun Zhang
            yzhangal Yongjun Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment