[ https://issues.apache.org/jira/browse/HDFS-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282014#comment-13282014 ]
Todd Lipcon commented on HDFS-2988: ----------------------------------- Hi Miomir. Thanks for your interest. You can start working on it without it being assigned -- though assigning is nice because it signifies that you're working on it. I'll assign this to you. > Improve error message when storage directory lock fails > ------------------------------------------------------- > > Key: HDFS-2988 > URL: https://issues.apache.org/jira/browse/HDFS-2988 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Reporter: Todd Lipcon > Priority: Minor > Labels: newbie > > Currently, the error message is fairly opaque to a non-developer ("Cannot > lock storage" or something). Instead, we should have some improvments: > - when we create the in_use.lock file, we should write the hostname/PID that > locked the file > - if the lock fails, and in_use.lock exists, the error message should say > something like "It appears that another namenode (pid 23423 on host > foo.example.com) has already locked the storage directory." > - if the lock fails, and no lock file exists, the error message should say > something like "if this storage directory is mounted via NFS, ensure that the > appropriate nfs lock services are running." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira