[
https://issues.apache.org/jira/browse/FLUME-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh resolved FLUME-52.
---------------------------------
Resolution: Not A Problem
Since this is all based on the clock at the master, I don' think this is really
a problem. For purists, ZK master 2.0 will possibly address this problem.
> Heartbeat code still uses timestamp rather than logical clock to decide if
> config is up-to-date
> -----------------------------------------------------------------------------------------------
>
> Key: FLUME-52
> URL: https://issues.apache.org/jira/browse/FLUME-52
> Project: Flume
> Issue Type: Bug
> Components: Master, Node, Sinks+Sources
> Affects Versions: v0.9.0
> Reporter: Disabled imported user
>
> There are, alas, many places where Flume is still using physical timestamps
> rather than logical ones for config versions.
> e.g. in MasterClientServer.java, in heartbeat(...)
> if (cfg == null || version < cfg.getTimestamp()) {
> configChanged = true;
> // version sent by node is older than current, return true to force
> config
> // upgrade
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
