[jira] [Updated] (STORM-2722) JMSSpout test fails way too often

[Robert Joseph Evans (JIRA)]

 [ 
https://issues.apache.org/jira/browse/STORM-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Joseph Evans updated STORM-2722:
---
Summary: JMSSpout test fails way too often  (was: JMsSpout test fails way 
too often)

> JMSSpout test fails way too often
> -
>
> Key: STORM-2722
> URL: https://issues.apache.org/jira/browse/STORM-2722
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-jms
>Affects Versions: 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {code}
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:92)
>   at org.junit.Assert.assertTrue(Assert.java:43)
>   at org.junit.Assert.assertTrue(Assert.java:54)
>   at 
> org.apache.storm.jms.spout.JmsSpoutTest.testFailure(JmsSpoutTest.java:62)
> {code}
> Which corresponds to 
> https://github.com/apache/storm/blob/d6e5e6d4e0a20c4c9f0ce0e3000e730dcb4700da/external/storm-jms/src/test/java/org/apache/storm/jms/spout/JmsSpoutTest.java?utf8=%E2%9C%93#L62



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (STORM-2742) Logviewer leaking file descriptors

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/STORM-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated STORM-2742:
--
Labels: pull-request-available  (was: )

> Logviewer leaking file descriptors
> --
>
> Key: STORM-2742
> URL: https://issues.apache.org/jira/browse/STORM-2742
> Project: Apache Storm
>  Issue Type: Bug
>Reporter: Kyle Nusbaum
>Assignee: Kyle Nusbaum
>  Labels: pull-request-available
>
> The logviewer leaks file descriptors from the search module.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (STORM-2722) JMsSpout test fails way too often

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/STORM-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated STORM-2722:
--
Labels: pull-request-available  (was: )

> JMsSpout test fails way too often
> -
>
> Key: STORM-2722
> URL: https://issues.apache.org/jira/browse/STORM-2722
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-jms
>Affects Versions: 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>  Labels: pull-request-available
>
> {code}
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:92)
>   at org.junit.Assert.assertTrue(Assert.java:43)
>   at org.junit.Assert.assertTrue(Assert.java:54)
>   at 
> org.apache.storm.jms.spout.JmsSpoutTest.testFailure(JmsSpoutTest.java:62)
> {code}
> Which corresponds to 
> https://github.com/apache/storm/blob/d6e5e6d4e0a20c4c9f0ce0e3000e730dcb4700da/external/storm-jms/src/test/java/org/apache/storm/jms/spout/JmsSpoutTest.java?utf8=%E2%9C%93#L62



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (STORM-2722) JMsSpout test fails way too often

[Robert Joseph Evans (JIRA)]

[ 
https://issues.apache.org/jira/browse/STORM-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170552#comment-16170552
 ] 

Robert Joseph Evans commented on STORM-2722:


I did some debugging and it turns out that the different tests are conflicting 
with each other.  Old spouts are not gone all the way by the time the new test 
starts, which results in the message going to the wrong spout so the test fails.

> JMsSpout test fails way too often
> -
>
> Key: STORM-2722
> URL: https://issues.apache.org/jira/browse/STORM-2722
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-jms
>Affects Versions: 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> {code}
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:92)
>   at org.junit.Assert.assertTrue(Assert.java:43)
>   at org.junit.Assert.assertTrue(Assert.java:54)
>   at 
> org.apache.storm.jms.spout.JmsSpoutTest.testFailure(JmsSpoutTest.java:62)
> {code}
> Which corresponds to 
> https://github.com/apache/storm/blob/d6e5e6d4e0a20c4c9f0ce0e3000e730dcb4700da/external/storm-jms/src/test/java/org/apache/storm/jms/spout/JmsSpoutTest.java?utf8=%E2%9C%93#L62



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (STORM-2722) JMsSpout test fails way too often

[Robert Joseph Evans (JIRA)]

 [ 
https://issues.apache.org/jira/browse/STORM-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Joseph Evans reassigned STORM-2722:
--

Assignee: Robert Joseph Evans

> JMsSpout test fails way too often
> -
>
> Key: STORM-2722
> URL: https://issues.apache.org/jira/browse/STORM-2722
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-jms
>Affects Versions: 2.0.0
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>
> {code}
> java.lang.AssertionError: null
>   at org.junit.Assert.fail(Assert.java:92)
>   at org.junit.Assert.assertTrue(Assert.java:43)
>   at org.junit.Assert.assertTrue(Assert.java:54)
>   at 
> org.apache.storm.jms.spout.JmsSpoutTest.testFailure(JmsSpoutTest.java:62)
> {code}
> Which corresponds to 
> https://github.com/apache/storm/blob/d6e5e6d4e0a20c4c9f0ce0e3000e730dcb4700da/external/storm-jms/src/test/java/org/apache/storm/jms/spout/JmsSpoutTest.java?utf8=%E2%9C%93#L62



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (STORM-2740) Add caching of some blobs in nimbus to improve performance

[Robert Joseph Evans (JIRA)]

 [ 
https://issues.apache.org/jira/browse/STORM-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Joseph Evans resolved STORM-2740.

   Resolution: Fixed
Fix Version/s: 2.0.0

Merged this into master

> Add caching of some blobs in nimbus to improve performance
> --
>
> Key: STORM-2740
> URL: https://issues.apache.org/jira/browse/STORM-2740
> Project: Apache Storm
>  Issue Type: Improvement
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> In nimbus we read the topology and the topology config from the blob store 
> all the time.  Even multiple times for a single thrift call.  It would really 
> be great if we could cache these instead of rereading them all the time. (We 
> have found it is a cause of the UI being slow in some cases).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (STORM-2741) Add in config options for metrics consumer cpu and memory

[Robert Joseph Evans (JIRA)]

 [ 
https://issues.apache.org/jira/browse/STORM-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Joseph Evans resolved STORM-2741.

   Resolution: Fixed
Fix Version/s: 2.0.0

Thanks [~ethanli],

I merged this into master.  Keep up the really good work.

> Add in config options for metrics consumer cpu and memory
> -
>
> Key: STORM-2741
> URL: https://issues.apache.org/jira/browse/STORM-2741
> Project: Apache Storm
>  Issue Type: Improvement
>Reporter: Ethan Li
>Assignee: Ethan Li
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 2.0.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Similar to STORM-2730, we want to add in configurations for metric consumer 
> cpu and memory requirements instead of just using 
> topology.component.resources.onheap.memory.mb etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (STORM-2607) [kafka-client] Consumer group every time with lag 1

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/STORM-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated STORM-2607:
--
Labels: pull-request-available  (was: )

> [kafka-client] Consumer group every time with lag 1
> ---
>
> Key: STORM-2607
> URL: https://issues.apache.org/jira/browse/STORM-2607
> Project: Apache Storm
>  Issue Type: Bug
>  Components: storm-kafka-client
>Affects Versions: 2.0.0, 1.1.1
>Reporter: Rodolfo Ribeiro SIlva
>Assignee: Hugo Louro
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> When i put a message a partition, the storm-kafka-client consume this message.
> But storm-kafka-client commit the offset -1.
> storm-kafka-client: 1.1.0
> storm-core : 1.1.0
> kafka: 0.10.2.0
> Steps to bug
> #1 - Insert message in kafka
> #2 - Read with storm Spout this topic
> #3 - Get the offset for the consumer group and the offset is always offset -1
> The KafkaSpoutConfig
> protected static KafkaSpoutConfig newKafkaSpoutConfig() {
>   return KafkaSpoutConfig.builder("192.168.57.11:9092", "topic").
>   setGroupId("storm").setOffsetCommitPeriodMs(10_000).
>   
> setMaxUncommittedOffsets(100_).setRetry(newRetryService())
>   .build();
>   }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)