[jira] [Commented] (STORM-1747) storm-kafka-client KafkaSpoutRetryExponentialBackoff throws exception

[ https://issues.apache.org/jira/browse/STORM-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265078#comment-15265078 ] Sriharsha Chintalapani commented on STORM-1747: --- [~flisky] can you add kafka version details

[jira] [Updated] (STORM-1747) storm-kafka-client KafkaSpoutRetryExponentialBackoff throws exception

[ https://issues.apache.org/jira/browse/STORM-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated STORM-1747: -- Assignee: Hugo Louro > storm-kafka-client KafkaSpoutRetryExponentialBackoff

Re: [VOTE] Release Apache Storm 1.0.1 (rc3)

+1 (Non binding) 2016-04-30 5:28 GMT+08:00 P. Taylor Goetz : > If at first you don't succeed... ;) > > This is a call to vote on releasing Apache Storm 1.0.1 (rc3) > > Full list of changes in this release: > > >

[VOTE] Release Apache Storm 1.0.1 (rc3)

If at first you don't succeed... ;) This is a call to vote on releasing Apache Storm 1.0.1 (rc3) Full list of changes in this release: https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=b5c16f919ad4099e6fb25f1095c9af8b64ac9f91 The tag/commit to be voted upon is

[GitHub] storm pull request: KafkaSpout README for storm-kafka-client (Kafk...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1383 --- 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

[jira] [Created] (STORM-1749) Fix storm-starter links in the github code

Abhishek Agarwal created STORM-1749: --- Summary: Fix storm-starter links in the github code Key: STORM-1749 URL: https://issues.apache.org/jira/browse/STORM-1749 Project: Apache Storm Issue

[jira] [Commented] (STORM-1741) storm-env.sh unconditionally sets JAVA_HOME

[ https://issues.apache.org/jira/browse/STORM-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264653#comment-15264653 ] ASF GitHub Bot commented on STORM-1741: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (STORM-1741) storm-env.sh unconditionally sets JAVA_HOME

[ https://issues.apache.org/jira/browse/STORM-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1741. Resolution: Fixed > storm-env.sh unconditionally sets JAVA_HOME >

[GitHub] storm pull request: STORM-1741: remove unconditional setting of JA...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1377 --- 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 pull request: KafkaSpout README for storm-kafka-client (Kafk...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1383#issuecomment-215865676 +1 Since this is a documentation-only patch, and is a big improvement, I'd like to pull this into 1.0.1 rc3. If there are any objections, we can always

[jira] [Commented] (STORM-1646) Intermittent test failures in storm-kafka unit tests

[ https://issues.apache.org/jira/browse/STORM-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264629#comment-15264629 ] ASF GitHub Bot commented on STORM-1646: --- Github user ppoulosk closed the pull request at:

[jira] [Commented] (STORM-1646) Intermittent test failures in storm-kafka unit tests

[ https://issues.apache.org/jira/browse/STORM-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264630#comment-15264630 ] ASF GitHub Bot commented on STORM-1646: --- GitHub user ppoulosk reopened a pull request:

[GitHub] storm pull request: [STORM-1646] Fix Kafka unit tests

Github user ppoulosk closed the pull request at: https://github.com/apache/storm/pull/1335 --- 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 pull request: [STORM-1646] Fix Kafka unit tests

GitHub user ppoulosk reopened a pull request: https://github.com/apache/storm/pull/1335 [STORM-1646] Fix Kafka unit tests This fixes two unit test failures in external/kafka I saw when running tests repeatedly, especially on low resource VMs. There was a race in the

[GitHub] storm pull request: KafkaSpout README for storm-kafka-client (Kafk...

Github user hmcl commented on the pull request: https://github.com/apache/storm/pull/1383#issuecomment-215857762 @ptgoetz @harshach can you please review. 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

[GitHub] storm pull request: KafkaSpout README for storm-kafka-client (Kafk...

GitHub user hmcl opened a pull request: https://github.com/apache/storm/pull/1383 KafkaSpout README for storm-kafka-client (Kafka new Consumer API) You can merge this pull request into a Git repository by running: $ git pull https://github.com/hmcl/storm-apache

[jira] [Commented] (STORM-1741) storm-env.sh unconditionally sets JAVA_HOME

[ https://issues.apache.org/jira/browse/STORM-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264610#comment-15264610 ] ASF GitHub Bot commented on STORM-1741: --- Github user abhishekagarwal87 commented on the pull

[GitHub] storm pull request: STORM-1741: remove unconditional setting of JA...

Github user abhishekagarwal87 commented on the pull request: https://github.com/apache/storm/pull/1377#issuecomment-215856040 +1 --- 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

[GitHub] storm pull request: STORM-1741: remove unconditional setting of JA...

Github user erikdw commented on the pull request: https://github.com/apache/storm/pull/1377#issuecomment-215852916 Merge away! Thanks for the update. --- 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

[jira] [Commented] (STORM-1741) storm-env.sh unconditionally sets JAVA_HOME

[ https://issues.apache.org/jira/browse/STORM-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264581#comment-15264581 ] ASF GitHub Bot commented on STORM-1741: --- Github user erikdw commented on the pull request:

[jira] [Created] (STORM-1748) Better Trident Spout Names

Derek Dagit created STORM-1748: -- Summary: Better Trident Spout Names Key: STORM-1748 URL: https://issues.apache.org/jira/browse/STORM-1748 Project: Apache Storm Issue Type: Improvement

[jira] [Commented] (STORM-1646) Intermittent test failures in storm-kafka unit tests

[ https://issues.apache.org/jira/browse/STORM-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264451#comment-15264451 ] ASF GitHub Bot commented on STORM-1646: --- Github user jerrypeng commented on the pull request:

[GitHub] storm pull request: [STORM-1646] Fix Kafka unit tests

Github user jerrypeng commented on the pull request: https://github.com/apache/storm/pull/1335#issuecomment-215831984 +1 --- 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

[jira] [Commented] (STORM-1707) Improve supervisor latency by removing 2-min wait

[ https://issues.apache.org/jira/browse/STORM-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264413#comment-15264413 ] ASF GitHub Bot commented on STORM-1707: --- Github user jerrypeng commented on the pull request:

[GitHub] storm pull request: [STORM-1707] Remove two minute timeout after w...

Github user jerrypeng commented on the pull request: https://github.com/apache/storm/pull/1370#issuecomment-215826814 +1 --- 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

[jira] [Commented] (STORM-1725) Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap not to throw Exception

[ https://issues.apache.org/jira/browse/STORM-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264296#comment-15264296 ] ASF GitHub Bot commented on STORM-1725: --- Github user hmcl commented on the pull request:

[GitHub] storm pull request: STORM-1725: Kafka Spout New Consumer API - Kaf...

Github user hmcl commented on the pull request: https://github.com/apache/storm/pull/1382#issuecomment-215794086 This is a cherry-pick of the commit that went in into the 1.x-branch --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[jira] [Commented] (STORM-1725) Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap not to throw Exception

[ https://issues.apache.org/jira/browse/STORM-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264293#comment-15264293 ] ASF GitHub Bot commented on STORM-1725: --- GitHub user hmcl opened a pull request:

[GitHub] storm pull request: STORM-1725: Kafka Spout New Consumer API - Kaf...

GitHub user hmcl opened a pull request: https://github.com/apache/storm/pull/1382 STORM-1725: Kafka Spout New Consumer API - KafkaSpoutRetryExponentialBackoff method should use HashMap instead of TreeMap not to throw Exception - Replace TreeMap with HashMap You can merge this

[jira] [Commented] (STORM-1741) storm-env.sh unconditionally sets JAVA_HOME

[ https://issues.apache.org/jira/browse/STORM-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264289#comment-15264289 ] ASF GitHub Bot commented on STORM-1741: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: STORM-1741: remove unconditional setting of JA...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1377#issuecomment-215792468 As this is a very minor change that fixes a blocker, if there are no objections I will merge it in order to proceed with the 1.0.1 rc3 release. If there are any

[jira] [Resolved] (STORM-1739) Minor JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1739. Resolution: Fixed Fix Version/s: 0.10.2 1.0.1

[jira] [Comment Edited] (STORM-1739) Minor JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264271#comment-15264271 ] P. Taylor Goetz edited comment on STORM-1739 at 4/29/16 4:19 PM: - Github

[GitHub] storm pull request: STORM-1739 (0.10.x) update the mini JAVA versi...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1368 --- 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

[jira] [Updated] (STORM-1739) Minor JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1739: --- Summary: Minor JAVA version dependency is wrong in 0.10.0 and above. (was: Mini JAVA version

[jira] [Commented] (STORM-1739) Mini JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264279#comment-15264279 ] ASF GitHub Bot commented on STORM-1739: --- Github user asfgit closed the pull request at:

[jira] [Commented] (STORM-1739) Mini JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264280#comment-15264280 ] ASF GitHub Bot commented on STORM-1739: --- Github user asfgit closed the pull request at:

[jira] [Commented] (STORM-1739) Mini JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264278#comment-15264278 ] ASF GitHub Bot commented on STORM-1739: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request: STORM-1739 (master) update the mini JAVA versi...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1366 --- 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 pull request: STORM-1739 (1.x) update the mini JAVA version ...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1367 --- 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

[jira] [Updated] (STORM-1737) storm-kafka-client has compilation errors with Apache Kafka 0.10

[ https://issues.apache.org/jira/browse/STORM-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-1737: -- Summary: storm-kafka-client has compilation errors with Apache Kafka 0.10 (was: storm-kaka-client has

[jira] [Commented] (STORM-1739) Mini JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264271#comment-15264271 ] ASF GitHub Bot commented on STORM-1739: --- Github user ptgoetz commented on the pull request:

[jira] [Commented] (STORM-1739) Mini JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264268#comment-15264268 ] ASF GitHub Bot commented on STORM-1739: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: STORM-1739 (0.10.x) update the mini JAVA versi...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1368#issuecomment-215784896 =1 --- 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

[jira] [Commented] (STORM-1739) Mini JAVA version dependency is wrong in 0.10.0 and above.

[ https://issues.apache.org/jira/browse/STORM-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264269#comment-15264269 ] ASF GitHub Bot commented on STORM-1739: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: STORM-1739 (1.x) update the mini JAVA version ...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1367#issuecomment-215784820 +1 --- 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

[GitHub] storm pull request: STORM-1739 (master) update the mini JAVA versi...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1366#issuecomment-215784757 +1 --- 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

[jira] [Resolved] (STORM-1727) document 1.0 package renaming and how to use the migration tool

[ https://issues.apache.org/jira/browse/STORM-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1727. Resolution: Fixed Fix Version/s: 1.0.1 Thanks [~vesense], merged to 1.x-branch. >

[GitHub] storm pull request: STORM-1727: add storm 1.0.0 rename note

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1358 --- 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

[jira] [Commented] (STORM-1727) document 1.0 package renaming and how to use the migration tool

[ https://issues.apache.org/jira/browse/STORM-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264259#comment-15264259 ] ASF GitHub Bot commented on STORM-1727: --- Github user asfgit closed the pull request at:

[jira] [Updated] (STORM-1727) document 1.0 package renaming and how to use the migration tool

[ https://issues.apache.org/jira/browse/STORM-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz updated STORM-1727: --- Summary: document 1.0 package renaming and how to use the migration tool (was: add storm

[jira] [Commented] (STORM-1727) add storm 1.0.0 rename note

[ https://issues.apache.org/jira/browse/STORM-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264251#comment-15264251 ] ASF GitHub Bot commented on STORM-1727: --- Github user ptgoetz commented on the pull request:

[GitHub] storm pull request: STORM-1727: add storm 1.0.0 rename note

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1358#issuecomment-215780240 +1 --- 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

[jira] [Resolved] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] P. Taylor Goetz resolved STORM-1733. Resolution: Fixed Fix Version/s: 1.0.1 2.0.0

[jira] [Commented] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264231#comment-15264231 ] ASF GitHub Bot commented on STORM-1733: --- Github user ptgoetz commented on the pull request:

[jira] [Commented] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264232#comment-15264232 ] ASF GitHub Bot commented on STORM-1733: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request: STORM-1733 (0.10.x) Flush stdout and stderr be...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1373 --- 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

[jira] [Commented] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264213#comment-15264213 ] ASF GitHub Bot commented on STORM-1733: --- Github user asfgit closed the pull request at:

[GitHub] storm pull request: STORM-1733 (0.1.x) Flush stdout and stderr bef...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1374 --- 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 pull request: STORM-1733 (0.1.x) Flush stdout and stderr bef...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1374#issuecomment-215760873 +1 @arunmahadevan I will merge for 1.0.1 rc3. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[jira] [Commented] (STORM-1733) Logs from bin/storm are lost because stdout and stderr are not flushed

[ https://issues.apache.org/jira/browse/STORM-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264197#comment-15264197 ] ASF GitHub Bot commented on STORM-1733: --- Github user ptgoetz commented on the pull request:

[jira] [Commented] (STORM-1707) Improve supervisor latency by removing 2-min wait

[ https://issues.apache.org/jira/browse/STORM-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264142#comment-15264142 ] ASF GitHub Bot commented on STORM-1707: --- Github user redsanket commented on the pull request:

[GitHub] storm pull request: [STORM-1707] Remove two minute timeout after w...

Github user redsanket commented on the pull request: https://github.com/apache/storm/pull/1370#issuecomment-215741544 LGTM +1 --- 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

[jira] [Commented] (STORM-1646) Intermittent test failures in storm-kafka unit tests

[ https://issues.apache.org/jira/browse/STORM-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264114#comment-15264114 ] ASF GitHub Bot commented on STORM-1646: --- Github user ppoulosk commented on the pull request:

[GitHub] storm pull request: [STORM-1646] Fix Kafka unit tests

Github user ppoulosk commented on the pull request: https://github.com/apache/storm/pull/1335#issuecomment-215733730 Changed usage of metadata.fetch.timeout.ms in KafkaBoltTest as well. --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

Github user srdo commented on a diff in the pull request: https://github.com/apache/storm/pull/1381#discussion_r61565774 --- Diff: external/storm-kafka/src/jvm/org/apache/storm/kafka/KafkaUtils.java --- @@ -213,7 +213,9 @@ public static ByteBufferMessageSet

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263951#comment-15263951 ] ASF GitHub Bot commented on STORM-1746: --- Github user srdo commented on a diff in the pull request:

[jira] [Commented] (STORM-1723) Introduce ClusterMetricsConsumer

[ https://issues.apache.org/jira/browse/STORM-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263945#comment-15263945 ] ASF GitHub Bot commented on STORM-1723: --- Github user abhishekagarwal87 commented on a diff in the

[GitHub] storm pull request: STORM-1723 (1.x) Introduce ClusterMetricsConsu...

Github user abhishekagarwal87 commented on a diff in the pull request: https://github.com/apache/storm/pull/1352#discussion_r61565297 --- Diff: conf/defaults.yaml --- @@ -285,3 +285,6 @@ pacemaker.kerberos.users: [] #default storm daemon metrics reporter plugins

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

Github user abhishekagarwal87 commented on a diff in the pull request: https://github.com/apache/storm/pull/1381#discussion_r61565123 --- Diff: external/storm-kafka/src/jvm/org/apache/storm/kafka/KafkaUtils.java --- @@ -213,7 +213,9 @@ public static ByteBufferMessageSet

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

GitHub user srdo reopened a pull request: https://github.com/apache/storm/pull/1381 STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION log to warn from error This error is transient most of the time and will occur during normal operation. Downgrading it to warning makes the error log

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

Github user srdo closed the pull request at: https://github.com/apache/storm/pull/1381 --- 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 pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

Github user srdo commented on the pull request: https://github.com/apache/storm/pull/1381#issuecomment-215688879 Looks like a flaky test. Going to try again. --- 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

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263920#comment-15263920 ] ASF GitHub Bot commented on STORM-1746: --- Github user srdo commented on the pull request:

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263921#comment-15263921 ] ASF GitHub Bot commented on STORM-1746: --- Github user srdo closed the pull request at:

[jira] [Created] (STORM-1747) storm-kafka-client KafkaSpoutRetryExponentialBackoff throws exception

Jifeng Yin created STORM-1747: - Summary: storm-kafka-client KafkaSpoutRetryExponentialBackoff throws exception Key: STORM-1747 URL: https://issues.apache.org/jira/browse/STORM-1747 Project: Apache Storm

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263895#comment-15263895 ] ASF GitHub Bot commented on STORM-1746: --- Github user srdo commented on the pull request:

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

Github user srdo commented on the pull request: https://github.com/apache/storm/pull/1381#issuecomment-215683426 This has the effect of downgrading all errors from fetch to warning level. Maybe the error log in KafkaUtils should be added back with a check for whether it's

Re: Thought on complete latency

@Jungtaek, Yes you're right. Since most of our use cases are multi-thread spouts, this is not a problem for us. As to Storm, I think we can use your second workaround for now, and re-evaluate this when we finish porting multi-thread spout in Phase 2. On Fri, Apr 29, 2016 at 6:10 PM, Jungtaek Lim

[GitHub] storm pull request: [WIP] STORM-1742 (1.x) More accurate 'complete...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1379#issuecomment-215680119 If anyone jump on this and help performance tests then I'd be really appreciated. --- If your project is set up for it, you can reply to this email and have your

[jira] [Commented] (STORM-1742) More accurate 'complete latency'

[ https://issues.apache.org/jira/browse/STORM-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263880#comment-15263880 ] ASF GitHub Bot commented on STORM-1742: --- Github user HeartSaVioR commented on the pull request:

Re: Thought on complete latency

FYI: Issue STORM-1742 and related pull request (WIP) #1379 are available. I've also done with functional test so that you can easily see what I'm claiming. Thanks, Jungtaek Lim (HeartSaVioR) 2016년 4월

[jira] [Commented] (STORM-1723) Introduce ClusterMetricsConsumer

[ https://issues.apache.org/jira/browse/STORM-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263849#comment-15263849 ] ASF GitHub Bot commented on STORM-1723: --- Github user HeartSaVioR commented on a diff in the pull

[GitHub] storm pull request: STORM-1723 (1.x) Introduce ClusterMetricsConsu...

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/1352#discussion_r61556669 --- Diff: conf/defaults.yaml --- @@ -285,3 +285,6 @@ pacemaker.kerberos.users: [] #default storm daemon metrics reporter plugins

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263848#comment-15263848 ] ASF GitHub Bot commented on STORM-1746: --- Github user abhishekagarwal87 commented on a diff in the

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263836#comment-15263836 ] ASF GitHub Bot commented on STORM-1746: --- Github user srdo commented on a diff in the pull request:

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

Github user srdo commented on a diff in the pull request: https://github.com/apache/storm/pull/1381#discussion_r61555375 --- Diff: external/storm-kafka/src/jvm/org/apache/storm/kafka/KafkaUtils.java --- @@ -213,7 +213,11 @@ public static ByteBufferMessageSet

[jira] [Commented] (STORM-1723) Introduce ClusterMetricsConsumer

[ https://issues.apache.org/jira/browse/STORM-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263835#comment-15263835 ] ASF GitHub Bot commented on STORM-1723: --- Github user abhishekagarwal87 commented on a diff in the

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263810#comment-15263810 ] ASF GitHub Bot commented on STORM-1746: --- Github user abhishekagarwal87 commented on a diff in the

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

Github user abhishekagarwal87 commented on a diff in the pull request: https://github.com/apache/storm/pull/1381#discussion_r61552972 --- Diff: external/storm-kafka/src/jvm/org/apache/storm/kafka/KafkaUtils.java --- @@ -213,7 +213,11 @@ public static ByteBufferMessageSet

[GitHub] storm pull request: STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION...

GitHub user srdo opened a pull request: https://github.com/apache/storm/pull/1381 STORM-1746: Downgrade NOT_LEADER_FOR_PARTITION log to warn from error This error is transient most of the time and will occur during normal operation. Downgrading it to warning makes the error log

[jira] [Commented] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

[ https://issues.apache.org/jira/browse/STORM-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263799#comment-15263799 ] ASF GitHub Bot commented on STORM-1746: --- GitHub user srdo opened a pull request:

[jira] [Created] (STORM-1746) Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils

Stig Rohde Døssing created STORM-1746: - Summary: Don't error log NOT_LEADER_FOR_PARTITION in KafkaUtils Key: STORM-1746 URL: https://issues.apache.org/jira/browse/STORM-1746 Project: Apache Storm

[jira] [Commented] (STORM-1742) More accurate 'complete latency'

[ https://issues.apache.org/jira/browse/STORM-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263786#comment-15263786 ] ASF GitHub Bot commented on STORM-1742: --- Github user HeartSaVioR commented on the pull request:

[GitHub] storm pull request: [WIP] STORM-1742 (1.x) More accurate 'complete...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/1379#issuecomment-215665798 I've done with functional tests. To experiment this behavior, I made a odd topology which modifies ExclamationTopology to let spout emits 1000 tuples and

[jira] [Commented] (STORM-1745) Add partition to PartitionManager logs where it's missing

[ https://issues.apache.org/jira/browse/STORM-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263764#comment-15263764 ] ASF GitHub Bot commented on STORM-1745: --- GitHub user srdo opened a pull request:

[GitHub] storm pull request: STORM-1745: Add partition to log output in Par...

GitHub user srdo opened a pull request: https://github.com/apache/storm/pull/1380 STORM-1745: Add partition to log output in PartitionManager Adding topic name and partition id to the log output makes it easier to debug when an issue arises. You can merge this pull request into a

[jira] [Created] (STORM-1745) Add partition to PartitionManager logs where it's missing

Stig Rohde Døssing created STORM-1745: - Summary: Add partition to PartitionManager logs where it's missing Key: STORM-1745 URL: https://issues.apache.org/jira/browse/STORM-1745 Project: Apache

Re: Thought on complete latency

sorry some correction which may confuse someone: With this circumstance there's no issue to keep it as is, since *users normally don't implemented ack() / fail() as long blocking method*. 2016년 4월 29일 (금) 오후 4:56, Jungtaek Lim 님이 작성: > Cody, > Thanks for join the

Re: Thought on complete latency

Cody, Thanks for join the conversation. If my understanding is right, the way JStorm handles complete latency is same to what Apache Storm currently does. Please refer https://github.com/apache/storm/blob/master/storm-core/src/clj/org/apache/storm/daemon/executor.clj#L545 What I really want to

  1   2   >