[
https://issues.apache.org/jira/browse/STORM-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep V Badiger updated STORM-870:
------------------------------------
Description:
The tuples emitted just before the spout restarts are never acked/failed after
the tuple tree completes. The spout never gets notified but the worker log for
the spout has the below log during its restart.
2015-06-18T14:47:01.430+0000 b.s.m.n.Client [ERROR] connection to
Netty-Client-localhost/127.0.0.1:6701 is unavailable
2015-06-18T14:47:01.433+0000 b.s.m.n.Client [DEBUG] successfully connected to
localhost/127.0.0.1:6701, [id: 0x9a243253, /127.0.0.1:36638 =>
localhost/127.0.0.1:6701] [attempt 1]
2015-06-18T14:47:01.433+0000 b.s.m.n.Client [ERROR] dropping 1 message(s)
destined for Netty-Client-localhost/127.0.0.1:6701
was:The tuples emitted just before the spout restarts are never acked/failed
after the tuple tree completes. There is no error log and the spout never gets
notified.
> Tuples emitted just before spout restarts are not acked/failed
> --------------------------------------------------------------
>
> Key: STORM-870
> URL: https://issues.apache.org/jira/browse/STORM-870
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.9.3, 0.9.4, 0.9.5
> Reporter: Pradeep V Badiger
>
> The tuples emitted just before the spout restarts are never acked/failed
> after the tuple tree completes. The spout never gets notified but the worker
> log for the spout has the below log during its restart.
> 2015-06-18T14:47:01.430+0000 b.s.m.n.Client [ERROR] connection to
> Netty-Client-localhost/127.0.0.1:6701 is unavailable
> 2015-06-18T14:47:01.433+0000 b.s.m.n.Client [DEBUG] successfully connected to
> localhost/127.0.0.1:6701, [id: 0x9a243253, /127.0.0.1:36638 =>
> localhost/127.0.0.1:6701] [attempt 1]
> 2015-06-18T14:47:01.433+0000 b.s.m.n.Client [ERROR] dropping 1 message(s)
> destined for Netty-Client-localhost/127.0.0.1:6701
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
