[jira] [Updated] (STORM-3171) java.lang.NoSuchMethodError in org.apache.storm:storm-kafka-monitor:jar:1.1.2 caused by dependency conflict issue

[ https://issues.apache.org/jira/browse/STORM-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LeoAugust19 updated STORM-3171: Description: Hi, we found a dependency conflict issue in  *org.apache.storm:storm-kafka-monitor:jar

[jira] [Resolved] (STORM-1311) port backtype.storm.ui.core to java

[ https://issues.apache.org/jira/browse/STORM-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-1311. Resolution: Fixed Fix Version/s: 2.0.0 Thanks [~govindmenon],   I merged t

[jira] [Resolved] (STORM-3170) DirectoryCleaner may not correctly report correct number of deleted files

[ https://issues.apache.org/jira/browse/STORM-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3170. Resolution: Fixed Thanks [~zhengdai],   I merged this into master. > DirectoryCl

[jira] [Updated] (STORM-3177) MockRemovableFile returns true on `#exists` even after `#delete` is called.

[ https://issues.apache.org/jira/browse/STORM-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhengdai Hu updated STORM-3177: --- Fix Version/s: (was: 2.0.0) > MockRemovableFile returns true on `#exists` even after `#delete` is

[jira] [Created] (STORM-3178) Decouple `ClientSupervisorUtils` and refactor metrics registration

Zhengdai Hu created STORM-3178: -- Summary: Decouple `ClientSupervisorUtils` and refactor metrics registration Key: STORM-3178 URL: https://issues.apache.org/jira/browse/STORM-3178 Project: Apache Storm

[jira] [Created] (STORM-3177) MockRemovableFile returns true on `#exists` even after `#delete` is called.

Zhengdai Hu created STORM-3177: -- Summary: MockRemovableFile returns true on `#exists` even after `#delete` is called. Key: STORM-3177 URL: https://issues.apache.org/jira/browse/STORM-3177 Project: Apache

[jira] [Resolved] (STORM-3166) Utils.threadDump does not account for dead threads

[ https://issues.apache.org/jira/browse/STORM-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing resolved STORM-3166. --- Resolution: Fixed Fix Version/s: 2.0.0 > Utils.threadDump does not account for

[jira] [Resolved] (STORM-3167) Flaky test in metrics_test.clj

[ https://issues.apache.org/jira/browse/STORM-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing resolved STORM-3167. --- Resolution: Fixed Fix Version/s: 2.0.0 > Flaky test in metrics_test.clj >

[jira] [Resolved] (STORM-3169) Misleading logviewer.cleanup.age.min

[ https://issues.apache.org/jira/browse/STORM-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing resolved STORM-3169. --- Resolution: Fixed Thanks for the fix [~zhengdai]. Merged to master. > Misleading log

[jira] [Resolved] (STORM-3168) AsyncLocalizer cleanup appears to crash

[ https://issues.apache.org/jira/browse/STORM-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3168. Resolution: Fixed Fix Version/s: 2.0.0 Thanks [~agresch], I merged this int

[jira] [Closed] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang closed STORM-3176. Resolution: Fixed the log has been modified > KafkaSpout commit offset occurs CommitFailedException which

[jira] [Updated] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang updated STORM-3176: - Description: KafkaSpout use the commitAsync api of Consumer, if the interval time between the call of co

[jira] [Reopened] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang reopened STORM-3176: -- modify some log > KafkaSpout commit offset occurs CommitFailedException which leads to worker > dead > --

[jira] [Closed] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing closed STORM-3176. - Resolution: Duplicate I think this is a symptom of using the KafkaConsumer.subscribe API.

[jira] [Reopened] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing reopened STORM-3176: --- > KafkaSpout commit offset occurs CommitFailedException which leads to worker > dead > -

[jira] [Closed] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang closed STORM-3176. Resolution: Fixed Fix Version/s: 1.2.0 > KafkaSpout commit offset occurs CommitFailedException which

[jira] [Updated] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang updated STORM-3176: - Affects Version/s: (was: 1.2.0) 1.1.2 > KafkaSpout commit offset occurs Commit

[jira] [Updated] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang updated STORM-3176: - Description: KafkaSpout use the commitAsync api of Consumer, if the interval time between the call of co

[jira] [Updated] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Wang updated STORM-3176: - Description: KafkaSpout use the commitAsync api of Consumer, if the interval time between call consumer.

[jira] [Updated] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

[ https://issues.apache.org/jira/browse/STORM-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3176: -- Labels: pull-request-available (was: ) > KafkaSpout commit offset occurs CommitFailedException

[jira] [Created] (STORM-3176) KafkaSpout commit offset occurs CommitFailedException which leads to worker dead

Matt Wang created STORM-3176: Summary: KafkaSpout commit offset occurs CommitFailedException which leads to worker dead Key: STORM-3176 URL: https://issues.apache.org/jira/browse/STORM-3176 Project: Apach