[
https://issues.apache.org/jira/browse/HADOOP-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678158#action_12678158
]
Ari Rabkin commented on HADOOP-5354:
------------------------------------
An alternative to using MD5 would be to store the adaptor ID in the checkpoint
file.
This would probably require modifying checkpointing to use some new command,
rather than "add" that explicitly sets the adaptor ID. This is probably not to
hard.
The advantage is that it's much easier for a human to reason about small
integer IDs than biggish MD5 hashes.
> AdaptorId should be persistent even after an agent restart
> ----------------------------------------------------------
>
> Key: HADOOP-5354
> URL: https://issues.apache.org/jira/browse/HADOOP-5354
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/chukwa
> Reporter: Jerome Boulon
>
> In case of agent restart, an adaptor may not get the same adaptorId.
> 1)The adaptorId is sent back to the remote application after the Add command.
> Now, let suppose the agent dies and restarts.
> Each new adaptor created from the checkpoint will now have another adaptorId
> .
> If the remote application tries to stop/shutdown only using the adaptorId
> received in step (1), the command may be sent to the wrong adaptor.
> if the adaptorId in for example an MD5 of the command line we don't need to
> save any additional information inside the checkpoint.
> This will change the current API from int to String.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
