[
https://issues.apache.org/jira/browse/HDFS-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233550#comment-13233550
]
Mingjie Lai commented on HDFS-3083:
-----------------------------------
Aaron. You're right for the root cause. The order of the configured namenodes
does make a difference.
Throwing StandbyException from SecreteManager is not perfect, but okay for me.
Good job.
> HA+security: failed to run a mapred job from yarn after a manual failover
> -------------------------------------------------------------------------
>
> Key: HDFS-3083
> URL: https://issues.apache.org/jira/browse/HDFS-3083
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, security
> Affects Versions: 0.24.0, 0.23.3
> Reporter: Mingjie Lai
> Assignee: Aaron T. Myers
> Priority: Critical
> Fix For: 0.24.0, 0.23.3
>
> Attachments: HDFS-3083-combined.patch
>
>
> Steps to reproduce:
> - turned on ha and security
> - run a mapred job, and wait to finish
> - failover to another namenode
> - run the mapred job again, it fails.
--
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
