[
https://issues.apache.org/jira/browse/HELIX-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667535#comment-16667535
]
Hudson commented on HELIX-764:
------------------------------
FAILURE: Integrated in Jenkins build helix #1547 (See
[https://builds.apache.org/job/helix/1547/])
[HELIX-764] TASK: Fix LiveInstanceCurrentState change flag (hulee: rev
d33d9efea25fe9d2bbbb9e84a4ce7614b544ef2d)
* (edit)
helix-core/src/main/java/org/apache/helix/controller/stages/ClusterDataCache.java
> [TASK] Fix LiveInstanceCurrentState change flag
> -----------------------------------------------
>
> Key: HELIX-764
> URL: https://issues.apache.org/jira/browse/HELIX-764
> Project: Apache Helix
> Issue Type: Improvement
> Reporter: Hunter L
> Assignee: Hunter L
> Priority: Major
>
> Previously, existsLiveInstanceOrCurrentStateChange was getting reset in
> ClusterDataCache when its getter was called. This was problematic because if
> there were multiple jobs or multiple workflows, whoever calls this getter
> would get the correct flag value, and the ensuing callers would get a false
> because the flag would have been reset. This RB fixes that bug by reseting
> the flat right in the beginning of refresh() call in ClusterDataCache, which
> allows all callers during that pipeline would get the same, correct value.
> Changelist:
> 1. Change the getter so that it does not reset the flag; instead, reset the
> flag in the beginning of refresh()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
