[
https://issues.apache.org/jira/browse/STORM-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498723#comment-14498723
]
ASF GitHub Bot commented on STORM-773:
--------------------------------------
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/526
STORM-773: STORM-772: Transactional test timeout too low on restart, and
InterruptedException
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-773
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/526.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #526
----
commit 933972abb47aa9b4ad87bc92d3ad7f79d21c9aee
Author: Robert (Bobby) Evans <[email protected]>
Date: 2015-04-16T20:58:37Z
STORM-773: Transactional test timout too low on restart
STORM-772: Interrupted and InterruptedIOException failures fixed
----
> backtype.storm.transactional-test fails periodically with timeout
> -----------------------------------------------------------------
>
> Key: STORM-773
> URL: https://issues.apache.org/jira/browse/STORM-773
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Robert Joseph Evans
> Attachments: failure.txt, success.txt
>
>
> I'm not totally sure what is happening here, but fairly frequently now on my
> mac running JDK8 backtype.storm.transactional-test will timeout.
> test-transactional-topology-restart seems to be the test in there that is
> getting the timeouts.
> I made some modifications to the test to just run that one test case, and to
> turn topology.debug on. I captured examples of it working and failing. I'll
> attach the logs files shortly. I am have not really had much time to dig
> into this, so I am not totally sure what is happening here. I can see from
> the logs that on the first run of the topology the failure case only emits 10
> batches, where as the successful case outputs many more. On the second run
> of the topology the failure case starts off at batch 11, but does not go
> beyond it. Where as the successful case keeps going.
> I'll try to find some time to look into it more, but I'm not sure how much
> time I will have in the near future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
