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

Namenode gets sticky if one of namenode storage volumes disappears (removed, unmounted, etc.)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.21.0
    • None
    • namenode
    • None

    Description

      While investigating failures on HDFS-1602 it became apparent that once a namenode storage volume is pulled out NN becomes completely "sticky" until FSImage:processIOError: removing storage move the storage from the active set. During this time none of normal NN operations are possible (e.g. creating a directory on HDFS timeouts eventually).

      In case of NFS this can be workaround'd with soft,intr,timeo,retrans settings. However, a better handling of the situation is apparently possible and needs to be implemented.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. HDFS-1602 NameNode storage failed replica restoration is broken

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              cos Konstantin I Boudnik
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: