chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-5) AdaptorId should be persistent even after an agent restart
Date Wed, 10 Jun 2009 05:31:09 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717920#action_12717920
] 

Ari Rabkin commented on CHUKWA-5:
---------------------------------

Is this on the roadmap for 0.2?  It's going to be a backwards-incompatible change to the agent
wire protocol, checkpoints, and initial_adaptors, I'm afraid, maybe more.  And so I'd like
to bite the bullet and do it sooner, rather than later.

> AdaptorId should be persistent even after an agent restart
> ----------------------------------------------------------
>
>                 Key: CHUKWA-5
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-5
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: data collection
>            Reporter: Jerome Boulon
>            Assignee: Cheng
>
> 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.


Mime
View raw message