[
https://issues.apache.org/jira/browse/MAPREDUCE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885787#action_12885787
]
Konstantin Boudnik commented on MAPREDUCE-1889:
-----------------------------------------------
- technically, you might end up with a situation where the same host is having
two different daemons, say JT and TT. Or NN and second DN. I believe in such
situation this new method {{+ public RemoteProcess getDaemonProcess(String
hostname) { }} will be deterministic. That's why we have {{HadoopDaemonInfo}}
class with a role for any daemon. Perhaps, the method should have an extra
parameter and return only daemons with a specific role.
- JavaDoc hasn't been changed for the changes of the signature
{[+ String pushConfig(String localDir) throws IOException;}}
Also, will changes of the method signature affect existing tests?
And please name the pachs {{something.patch}} instead of .txt or else.
> [herriot] Ability to restart a single node for pushconfig
> ---------------------------------------------------------
>
> Key: MAPREDUCE-1889
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1889
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: test
> Reporter: Balaji Rajagopalan
> Assignee: Balaji Rajagopalan
> Attachments: restartDaemon.txt, restartDaemon_1.txt
>
>
> Right now the pushconfig is supported only at a cluster level, this jira will
> introduce the functionality to be supported at node level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
