[
https://issues.apache.org/jira/browse/CURATOR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930614#comment-16930614
]
Jordan Zimmerman edited comment on CURATOR-540 at 9/16/19 2:40 PM:
-------------------------------------------------------------------
note: re-wording
[~honglun] what is the bug here? Are you confusing by the log message? I don't
understand what the issue is. You say "But the mode
"StartMode.BUILD_INITIAL_CACHE" should not send history, right?" but what
you're showing is a log message. You are not being clear about what the problem
is. I'm going to close this issue if it can't be explained clearly.
updating...
I think I may understand. When PathChildrenCache gets a CONNECTED/RECONNECTED
it forces a re-refresh of the cache. This can cause listeners to get called.
This has always been the case with PathChildrenCache, even in 2.7.0 (I just
checked). If you want to avoid this, call {{client.blockUntilConnected(...)}}
before starting your cache.
was (Author: randgalt):
note: re-wording
[~honglun] what is the bug here? Are you confusing by the log message? I don't
understand what the issue is. You say "But the mode
"StartMode.BUILD_INITIAL_CACHE" should not send history, right?" but what
you're showing is a log message. You are not being clear about what the problem
is. I'm going to close this issue if it can't be explained clearly.
> 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)
