[GitHub] storm pull request #1591: STORM-1038: Upgrade netty to 4.x in 1.x-branch

2016-09-24 Thread hsun-cnnxty
GitHub user hsun-cnnxty reopened a pull request: https://github.com/apache/storm/pull/1591 STORM-1038: Upgrade netty to 4.x in 1.x-branch This is to add the feature to 1.x-branch. The original PR for master branch is #728. You can merge this pull request into a Git repository by r

[GitHub] storm pull request #1591: STORM-1038: Upgrade netty to 4.x in 1.x-branch

2016-09-24 Thread hsun-cnnxty
Github user hsun-cnnxty closed the pull request at: https://github.com/apache/storm/pull/1591 --- 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] storm issue #1679: STORM-2087: storm-kafka-client - tuples not always being ...

2016-09-24 Thread jfenc91
Github user jfenc91 commented on the issue: https://github.com/apache/storm/pull/1679 I am on version 0.10.0.1. Interesting, didn't realize unclean leader election was a default... So ya I had that enabled. Turning that off now though! Thanks @srdo for the tip and hopefully that will

[GitHub] storm issue #1679: STORM-2087: storm-kafka-client - tuples not always being ...

2016-09-24 Thread srdo
Github user srdo commented on the issue: https://github.com/apache/storm/pull/1679 @jfenc91 Ouch. I've never seen LEO drop like that unless unclean leader election was enabled. Out of curiosity which Kafka version are you running, and do you have unclean leader election enabled for th

[GitHub] storm issue #1679: STORM-2087: storm-kafka-client - tuples not always being ...

2016-09-24 Thread jfenc91
Github user jfenc91 commented on the issue: https://github.com/apache/storm/pull/1679 @srdo @hmcl I tracked down one source of the "double acking" It looks like I am being switched to reading from an out of sync replica. Looking at my offsets: GROUP