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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 0.9.0
• Component/s: Master, Node, Sinks+Sources
• Assignee: Jonathan Hsieh
• Reporter: Disabled imported user
• Created: 14/Jul/10 17:55
• Updated: 19/Aug/11 02:57
• Resolved: 19/Aug/11 02:57

Description

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 }

Issue Links

• relates to: FLUME-617 ZK backed multimaster 2.0