Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/542#issuecomment-155928236
@revans2
Yes, as I described to [JIRA
issue](https://issues.apache.org/jira/browse/STORM-794?focusedCommentId=14526316&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14526316),
MasterBatchCoordinator doesn't play well with async loop, since it handles
emitting batch independently. MasterBatchCoordinator could make pending tuple
count always same to max spout pending in point of async loop's view, which
makes async loop to never trigger deactivate.
I'll do upmerge and let you know. Thanks!
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
