[
https://issues.apache.org/jira/browse/CURATOR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931823#comment-16931823
]
Jordan Zimmerman commented on CURATOR-540:
------------------------------------------
2.7 may not have handled CONNECTED (which was actually a bug) but it did handle
RECONNECTED which would have exhibited the same behavior. i.e. if there was a
connection event during the start of the cache and a quick RECONNECTED you'd
see the same rebuild behavior with events being posted,
> BUILD_INITIAL_CACHE mode will post history child on start
> ---------------------------------------------------------
>
> Key: CURATOR-540
> URL: https://issues.apache.org/jira/browse/CURATOR-540
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 2.12.0, 2.13.0
> Reporter: HonglunChen
> Priority: Major
> Attachments: image-2019-09-16-12-43-01-588.png
>
>
> I debugged and found the root cause : In PathChildrenCache, CONNECTED state
> is triggered before currentData initializes.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
