Namenode gets sticky if one of namenode storage volumes disappears (removed,
unmounted, etc.)
---------------------------------------------------------------------------------------------
Key: HDFS-1603
URL: https://issues.apache.org/jira/browse/HDFS-1603
Project: Hadoop HDFS
Issue Type: Bug
Components: name-node
Affects Versions: 0.21.0
Reporter: Konstantin Boudnik
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
