[jira] [Assigned] (FLUME-52) Heartbeat code still uses timestamp rather than logical clock to decide if config is up-to-date

["Jonathan Hsieh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hsieh reassigned FLUME-52:
-----------------------------------

    Assignee: Jonathan Hsieh

> 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
>            Assignee: Jonathan Hsieh
>
> 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