How can i avoid duplicate event processing when this situation arises. i
assuming all events which where processed by this supervisor node might be
replayed.
On Mon, Feb 2, 2015 at 8:22 PM, Harsha wrote:
> Tousif,
>You might be running into
> https://issues.apache.org/jira/browse/STOR
Tousif, You might be running into
https://issues.apache.org/jira/browse/STORM-130 . -Harsha
On Mon, Feb 2, 2015, at 12:28 AM, Tousif wrote:
> Thank you, Can you tell me why it might happen? i recently tried zk
> 3.3.3 with 0.9.2 and found incompatible than moved back again to 3.4.6
> . i was try
Thank you, Can you tell me why it might happen? i recently tried zk 3.3.3
with 0.9.2 and found incompatible than moved back again to 3.4.6 . i was
trying zk 3.3.3 coz 3.4.6 is disconnecting with one of the worker and
suspending.
On Mon, Feb 2, 2015 at 11:14 AM, Kosala Dissanayake
wrote:
> Clear
Clear your storm local directory and restart the supervisor.
On Fri, Jan 30, 2015 at 6:03 PM, Tousif wrote:
> one of the worker in storm is terminating with the following error.i'm
> using zookeeper 3.4.6 Here is the log.
>
> o.a.c.f.s.ConnectionStateManager [INFO] State change: CONNECTED 2015-0
one of the worker in storm is terminating with the following error.i'm
using zookeeper 3.4.6 Here is the log.
o.a.c.f.s.ConnectionStateManager [INFO] State change: CONNECTED 2015-01-30
08:25:04 o.a.c.f.s.ConnectionStateManager [WARN] There are no
ConnectionStateListeners registered. 2015-01-30 08:
