[jira] [Updated] (STORM-2738) The number of ackers should default to the number of actual running workers on RAS cluster

[ https://issues.apache.org/jira/browse/STORM-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Li updated STORM-2738: Summary: The number of ackers should default to the number of actual running workers on RAS cluster (was:

[jira] [Resolved] (STORM-2730) Add in config options for acker cpu and memory

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

[jira] [Updated] (STORM-2709) Release Apache Storm 1.1.2

[ https://issues.apache.org/jira/browse/STORM-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated STORM-2709: -- Fix Version/s: 1.1.2 > Release Apache Storm 1.1.2 > -- > >

[jira] [Updated] (STORM-2549) The fix for STORM-2343 is incomplete, and the spout can still get stuck on failed tuples

[ https://issues.apache.org/jira/browse/STORM-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2549: -- Labels: pull-request-available (was: ) > The fix for STORM-2343 is incomplete, and the spout

[jira] [Updated] (STORM-2710) Release Apache Storm 1.2.0

[ https://issues.apache.org/jira/browse/STORM-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated STORM-2710: -- Description: This is to track remaining issues on releasing Storm 1.2.0. These are in

[jira] [Resolved] (STORM-2494) KafkaSpout does not handle CommitFailedException

[ https://issues.apache.org/jira/browse/STORM-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro resolved STORM-2494. --- Resolution: Fixed Fix Version/s: 1.2.0 STORM-2640 also fixes STORM-2494 > KafkaSpout does not

[jira] [Updated] (STORM-2710) Release Apache Storm 1.2.0

[ https://issues.apache.org/jira/browse/STORM-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated STORM-2710: -- Fix Version/s: 1.2.0 > Release Apache Storm 1.2.0 > -- > >

[jira] [Resolved] (STORM-2736) o.a.s.b.BlobStoreUtils [ERROR] Could not update the blob with key

[ https://issues.apache.org/jira/browse/STORM-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-2736. Resolution: Fixed Fix Version/s: 1.1.2 1.2.0

[jira] [Created] (STORM-2738) The number of ackers doesn't default to the number of actual running workers on RAS cluster

Ethan Li created STORM-2738: --- Summary: The number of ackers doesn't default to the number of actual running workers on RAS cluster Key: STORM-2738 URL: https://issues.apache.org/jira/browse/STORM-2738

[jira] [Commented] (STORM-2629) Can't build site on Windows due to Nokogiri failing to install

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

[jira] [Updated] (STORM-2629) Can't build site on Windows due to Nokogiri failing to install

[ https://issues.apache.org/jira/browse/STORM-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2629: -- Labels: pull-request-available (was: ) > Can't build site on Windows due to Nokogiri failing

[jira] [Commented] (STORM-2693) Topology submission or kill takes too much time when topologies grow to a few hundred

[ https://issues.apache.org/jira/browse/STORM-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164246#comment-16164246 ] Jungtaek Lim commented on STORM-2693: - [~danny0405] Yes I think it should work. Then I don't think we

[jira] [Commented] (STORM-2171) blob recovery on a single host results in deadlock

[ https://issues.apache.org/jira/browse/STORM-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164339#comment-16164339 ] Jungtaek Lim commented on STORM-2171: - Just curious: Is this based on theory or are you experienced

[jira] [Updated] (STORM-2693) Topology submission or kill takes too much time when topologies grow to a few hundred

[ https://issues.apache.org/jira/browse/STORM-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2693: -- Labels: pull-request-available (was: ) > Topology submission or kill takes too much time when

[jira] [Resolved] (STORM-2675) KafkaTridentSpoutOpaque not committing offsets to Kafka

[ https://issues.apache.org/jira/browse/STORM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-2675. - Resolution: Fixed Fix Version/s: 1.2.0 Also merged into 1.x branch. >

[jira] [Updated] (STORM-2675) KafkaTridentSpoutOpaque not committing offsets to Kafka

[ https://issues.apache.org/jira/browse/STORM-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2675: -- Labels: pull-request-available (was: ) > KafkaTridentSpoutOpaque not committing offsets to

[jira] [Commented] (STORM-2171) blob recovery on a single host results in deadlock

[ https://issues.apache.org/jira/browse/STORM-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164627#comment-16164627 ] Robert Joseph Evans commented on STORM-2171: We actually saw this during some testing, but it