You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (Jira)" <ji...@apache.org> on 2019/09/16 14:37:00 UTC
[jira] [Comment Edited] (CURATOR-540) BUILD_INITIAL_CACHE mode will
post history child on start
[ 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:36 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.
was (Author: randgalt):
[~honglun] "But the mode "StartMode.BUILD_INITIAL_CACHE" should not send history, right?" - this is not correct. It won't send history about nodes it's creating but connection state changes are always sent to the PathChildrenCache listener. This has always been the case. If you want to avoid this, add a call to {{client.blockUntilConnected(...)}} before starting the cache.
> 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)