You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@curator.apache.org by ? ?? <wa...@outlook.com> on 2018/07/16 08:57:11 UTC

NodeCacheListener Fails to Get Called

Hi all,

I am using NodeCacheListener in Storm. A new NodeCache instance is created in each Bolt and started. And a NodeCacheListener is registered to the NodeCache instance. But it is observed that some NodeCacheListener did not get invoked. Did anyone of you ever encounter this issue? Any help is appreciated. Thanks in advance.

________________________________
wangchunchao@outlook.com

Re: NodeCacheListener Fails to Get Called

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
There's no issue with NodeCache that I know of. I would think that if there was we'd have heard it by now. But, who knows. If you can provide a sample that shows the problem it would help.

-Jordan

> On Jul 16, 2018, at 9:07 PM, ? ?? <wa...@outlook.com> wrote:
> 
> Jordan, thanks for your suggestion.
> 
> My question is whether it is possible that NodeCacheListener miss a node change event. If it is, when and how does it happen? I am using it in Storm's Bolts. Each Bolt task has a NodeCacheListener and all the NodeCacheListeners watch the same ZNode. But it is observed that only some NodeCacheListeners got invoked while others did not.
> 
> wangchunchao@outlook.com <ma...@outlook.com>
>  
> From: Jordan Zimmerman <ma...@jordanzimmerman.com>
> Date: 2018-07-17 03:06
> To: user <ma...@curator.apache.org>
> Subject: Re: NodeCacheListener Fails to Get Called
> You haven't given any information at all. Please provide a complete question and maybe someone can help.
> 
> -Jordan
> 
>> On Jul 16, 2018, at 3:57 AM, ? ?? <wangchunchao@outlook.com <ma...@outlook.com>> wrote:
>> 
>> Hi all,
>> 
>> I am using NodeCacheListener in Storm. A new NodeCache instance is created in each Bolt and started. And a NodeCacheListener is registered to the NodeCache instance. But it is observed that some NodeCacheListener did not get invoked. Did anyone of you ever encounter this issue? Any help is appreciated. Thanks in advance.
>> 
>> wangchunchao@outlook.com <ma...@outlook.com>

Re: Re: NodeCacheListener Fails to Get Called

Posted by ? ?? <wa...@outlook.com>.
Jordan, thanks for your suggestion.

My question is whether it is possible that NodeCacheListener miss a node change event. If it is, when and how does it happen? I am using it in Storm's Bolts. Each Bolt task has a NodeCacheListener and all the NodeCacheListeners watch the same ZNode. But it is observed that only some NodeCacheListeners got invoked while others did not.

________________________________
wangchunchao@outlook.com

From: Jordan Zimmerman<ma...@jordanzimmerman.com>
Date: 2018-07-17 03:06
To: user<ma...@curator.apache.org>
Subject: Re: NodeCacheListener Fails to Get Called
You haven't given any information at all. Please provide a complete question and maybe someone can help.

-Jordan

On Jul 16, 2018, at 3:57 AM, ? ?? <wa...@outlook.com>> wrote:

Hi all,

I am using NodeCacheListener in Storm. A new NodeCache instance is created in each Bolt and started. And a NodeCacheListener is registered to the NodeCache instance. But it is observed that some NodeCacheListener did not get invoked. Did anyone of you ever encounter this issue? Any help is appreciated. Thanks in advance.

________________________________
wangchunchao@outlook.com<ma...@outlook.com>


Re: NodeCacheListener Fails to Get Called

Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
You haven't given any information at all. Please provide a complete question and maybe someone can help.

-Jordan

> On Jul 16, 2018, at 3:57 AM, ? ?? <wa...@outlook.com> wrote:
> 
> Hi all,
> 
> I am using NodeCacheListener in Storm. A new NodeCache instance is created in each Bolt and started. And a NodeCacheListener is registered to the NodeCache instance. But it is observed that some NodeCacheListener did not get invoked. Did anyone of you ever encounter this issue? Any help is appreciated. Thanks in advance.
> 
> wangchunchao@outlook.com <ma...@outlook.com>