You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2013/05/16 20:15:16 UTC

[jira] [Created] (HDFS-4828) Make QJM epoch-related errors more understandable

Todd Lipcon created HDFS-4828:
---------------------------------

             Summary: Make QJM epoch-related errors more understandable
                 Key: HDFS-4828
                 URL: https://issues.apache.org/jira/browse/HDFS-4828
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: qjm
    Affects Versions: 3.0.0, 2.0.5-beta
            Reporter: Todd Lipcon


Since we started running QJM on production clusters, we've found that users are very confused by some of the error messages that it produces. For example, when a failover occurs and an old NN gets fenced out, it sees errors about its epoch being out of date. We should amend these errors to add text like "This is likely because another NameNode took over as Active." Potentially we can even include the other NN's hostname, timestamp it became active, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira