[
https://issues.apache.org/jira/browse/CHUKWA-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506867#comment-13506867
]
Sourygna Luangsay commented on CHUKWA-670:
------------------------------------------
Still, I don't really understand what would be the benefit to have a
centralized Zookeeper configuration system instead of using Puppet or Chef.
Maybe, what you want to do is getting sure that the collector list is always
"up-to-date" (that is, if a collector node fails, it will be immediately
removed from the list), so that there would be no HTTP time-out from an agent
trying to reach an unavailable collector. Is that your idea?
Could you please detail the use-case that gives you the need to implement this
ZK feature?
> Use ZooKeeper for collector list and adaptor check list
> -------------------------------------------------------
>
> Key: CHUKWA-670
> URL: https://issues.apache.org/jira/browse/CHUKWA-670
> Project: Chukwa
> Issue Type: New Feature
> Components: Data Collection
> Environment: Java, ZooKeeper, Chukwa
> Reporter: Eric Yang
>
> Agent is currently using local disk to storage check point file, and
> collector list. This can be hard to manage for large scale system that needs
> to be updated more frequently. The proposal is to have a new configuration
> in chukwa agent configuration file to enable ZooKeeper as the location to
> store check point file and collector list.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
