Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/818#issuecomment-151749882
For long running topologies using kafka spout, we have always ran into this
deadlock. It completely blocks the topology. Internally, we are already running
the
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/818
---
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
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/818#issuecomment-151603314
@abhishekagarwal87 @HeartSaVioR
I'm okay with canceling the current 0.9.6 release vote and cutting a new
release candidate if there is enough community support.
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/818#issuecomment-151670108
@ptgoetz @abhishekagarwal87
If we can cancel current release vote, and decide to cancel, I'll do
backport this to 0.9.6. Decision should be made.
---
If your
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/818#issuecomment-151053131
This PR is to backport STORM-1027 into 0.9.x branch. @HeartSaVioR can you
merge this?
---
If your project is set up for it, you can reply to this email and
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/818#issuecomment-151320836
@abhishekagarwal87
Vote for releasing 0.9.6 and 0.10.0 is in progress.
I heard from @ptgoetz that Storm 0.9.x line will be faded out, so I'm
expecting
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/818#issuecomment-151377374
can this not be released as part of 0.9.6? We see this deadlock regularly
in our kafka spout based topologies.
---
If your project is set up for it, you can
