Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/941#issuecomment-165193668
> It's an unlikely scenario and I might be paranoid, but what if the tests
were running on a cluster under heavy traffic? For instance, what if the tests
were to be run on OpenStack, and the test just happened to run when there is
unrelated heavy traffic (say, Hadoop shuffle) pressuring the switches?
This should be using the loopback device. I think the main problem here is
the CPU was too busy to have the thrift server reply within 30ms. If traffic
were the issue, we would see many more of our tests fail similarly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
