You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@fluo.apache.org by gi...@git.apache.org on 2017/05/16 18:33:01 UTC

[GitHub] keith-turner opened a new issue #839: Stress test hangs with unprocessed notifications.

keith-turner opened a new issue #839: Stress test hangs with unprocessed notifications.
URL: https://github.com/apache/incubator-fluo/issues/839

When running the Fluo Stress test locally against 1.1.0-SNAPSHOT, sometimes it hangs with unprocessed notifications. These notifications never get processed. I took head dump of the workers and see that the map that tracks notifications has entries in it that indicate notifications are queued. However nothing is being done with these.

```
14:05:18.307 [main] INFO o.a.fluo.cluster.runner.AppRunner - 39855 notifications are still outstanding. Will try again in 199 seconds...
14:08:37.515 [main] INFO o.a.fluo.cluster.runner.AppRunner - 39855 notifications are still outstanding. Will try again in 199 seconds...
14:11:56.717 [main] INFO o.a.fluo.cluster.runner.AppRunner - 39855 notifications are still outstanding. Will try again in 199 seconds...
14:15:15.922 [main] INFO o.a.fluo.cluster.runner.AppRunner - 39855 notifications are still outstanding. Will try again in 199 seconds...
14:18:35.123 [main] INFO o.a.fluo.cluster.runner.AppRunner - 39855 notifications are still outstanding. Will try again in 199 seconds...
```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

With regards,
Apache Git Services