[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-19 Thread Kai Zheng (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327398#comment-14327398 ] Kai Zheng commented on HDFS-7731: - Glad you get it work. > Can not start HA namenode with

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-19 Thread donhoff_h (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327395#comment-14327395 ] donhoff_h commented on HDFS-7731: - Hi, Zheng Kai and surendra The problem is really caused

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-16 Thread surendra singh lilhore (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323066#comment-14323066 ] surendra singh lilhore commented on HDFS-7731: -- Hi, You are getting UNKNOWN_

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread Kai Zheng (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304746#comment-14304746 ] Kai Zheng commented on HDFS-7731: - bq.The key version is same as the version in the keytab

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread donhoff_h (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304498#comment-14304498 ] donhoff_h commented on HDFS-7731: - Hi, Kihwal Lee The key version is same as the version i

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread Kihwal Lee (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303339#comment-14303339 ] Kihwal Lee commented on HDFS-7731: -- Check and compare kvno of QJM's SPN from a client and

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread donhoff_h (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303314#comment-14303314 ] donhoff_h commented on HDFS-7731: - Hi, Zheng Kai I checked my logs on JournalNodes. But th

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread Kai Zheng (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303265#comment-14303265 ] Kai Zheng commented on HDFS-7731: - Googling the error finds below. Please also check the DN

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread Kai Zheng (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303259#comment-14303259 ] Kai Zheng commented on HDFS-7731: - Looks like the error occurred while NN trying to read ed

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread donhoff_h (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303206#comment-14303206 ] donhoff_h commented on HDFS-7731: - Hi, Zheng Kai I'm sure my Kerberos principals and keyta

[jira] [Commented] (HDFS-7731) Can not start HA namenode with security enabled

2015-02-03 Thread Kai Zheng (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303160#comment-14303160 ] Kai Zheng commented on HDFS-7731: - The failure was caused with the following error: {noform