[jira] [Updated] (STORM-2535) test-reset-timeout is flaky. Replace with a more reliable test.
[ https://issues.apache.org/jira/browse/STORM-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2535: Fix Version/s: 1.1.2 1.2.0 > test-reset-timeout is flaky. Replace with a more reliable test. > --- > > Key: STORM-2535 > URL: https://issues.apache.org/jira/browse/STORM-2535 > Project: Apache Storm > Issue Type: Bug >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing > Labels: pull-request-available > Fix For: 2.0.0, 1.2.0, 1.1.2 > > Time Spent: 40m > Remaining Estimate: 0h > > test-reset-timeout is flaky, because the Time.sleep calls in the test bolt > can race with the calls to advanceClusterTime in the main thread. Also the > test breaks if the spout's pending map gets rotated at an unlucky time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (STORM-2808) Main UI gets some errors.
[
https://issues.apache.org/jira/browse/STORM-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-2808.
-
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~govindmenon], I merged into master.
> Main UI gets some errors.
> -
>
> Key: STORM-2808
> URL: https://issues.apache.org/jira/browse/STORM-2808
> Project: Apache Storm
> Issue Type: Bug
>Reporter: Robert Joseph Evans
>Assignee: Govind Menon
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I noticed that the UI is throwing exceptions...
> {code}
> java.lang.NullPointerException
> at clojure.lang.Numbers.minus(Numbers.java:3708)
> at
> org.apache.storm.ui.core$cluster_summary$iter__3372__3376$fn__3377.invoke(core.clj:430)
> at clojure.lang.LazySeq.sval(LazySeq.java:40)
> at clojure.lang.LazySeq.seq(LazySeq.java:49)
> at clojure.lang.RT.seq(RT.java:507)
> at clojure.core$seq__4128.invoke(core.clj:137)
> at clojure.core.protocols$seq_reduce.invoke(protocols.clj:26)
> at clojure.core.protocols$fn__6506.invoke(protocols.clj:100)
> at
> clojure.core.protocols$fn__6452$G__6447__6465.invoke(protocols.clj:13)
> at clojure.core$reduce.invoke(core.clj:6515)
> at org.apache.storm.ui.core$cluster_summary.invoke(core.clj:426)
> at org.apache.storm.ui.core$cluster_summary.invoke(core.clj:412)
> at org.apache.storm.ui.core$fn__3865.invoke(core.clj:1258)
> at compojure.core$make_route$fn__382.invoke(core.clj:100)
> at compojure.core$if_route$fn__370.invoke(core.clj:46)
> at compojure.core$if_method$fn__363.invoke(core.clj:31)
> at compojure.core$routing$fn__388.invoke(core.clj:113)
> at clojure.core$some.invoke(core.clj:2570)
> at compojure.core$routing.doInvoke(core.clj:113)
> at clojure.lang.RestFn.applyTo(RestFn.java:139)
> at clojure.core$apply.invoke(core.clj:632)
> at compojure.core$routes$fn__392.invoke(core.clj:118)
> at ring.middleware.json$wrap_json_params$fn__1800.invoke(json.clj:74)
> at
> ring.middleware.multipart_params$wrap_multipart_params$fn__1038.invoke(multipart_params.clj:172)
> at ring.middleware.reload$wrap_reload$fn__844.invoke(reload.clj:39)
> at
> org.apache.storm.ui.helpers$requests_middleware$fn__3110.invoke(helpers.clj:46)
> at org.apache.storm.ui.core$catch_errors$fn__4073.invoke(core.clj:1587)
> at
> ring.middleware.keyword_params$wrap_keyword_params$fn__2851.invoke(keyword_params.clj:36)
> at
> ring.middleware.nested_params$wrap_nested_params$fn__2891.invoke(nested_params.clj:89)
> at ring.middleware.params$wrap_params$fn__2823.invoke(params.clj:67)
> at
> ring.middleware.multipart_params$wrap_multipart_params$fn__1038.invoke(multipart_params.clj:172)
> at ring.middleware.flash$wrap_flash$fn__3096.invoke(flash.clj:39)
> at ring.middleware.session$wrap_session$fn__3081.invoke(session.clj:108)
> at
> ring.util.servlet$make_blocking_service_method$fn__2718.invoke(servlet.clj:113)
> at ring.util.servlet$servlet$fn__2729.invoke(servlet.clj:147)
> at
> ring.util.servlet.proxy$javax.servlet.http.HttpServlet$ff19274a.service(Unknown
> Source)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
> at
> org.apache.storm.logging.filters.AccessLoggingFilter.handle(AccessLoggingFilter.java:51)
> at
> org.apache.storm.logging.filters.AccessLoggingFilter.doFilter(AccessLoggingFilter.java:43)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)
> at
> org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:308)
> at
> org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:262)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:188)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1253)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:168)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:166)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1155)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:
[jira] [Comment Edited] (STORM-2810) Storm-hdfs tests are leaking resources
[ https://issues.apache.org/jira/browse/STORM-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248995#comment-16248995 ] Jungtaek Lim edited comment on STORM-2810 at 11/12/17 9:49 PM: --- [~Srdo] Thanks, I merged the patch into master. I noticed the failure of storm-hdfs in Travis CI with OpenJDK7 looks like consistent, and you also put 1.1.2 to affects version/s as well. Could you raise a PR against 1.x branch as well? Cause it doesn't look like clean cherry picking. Please let me know if you don't have time to do so, I'll try to craft it. was (Author: kabhwan): [~Srdo] Thanks, I merged the patch into master. I noticed the failure of storm-hdfs in Travis CI with OpenJDK7 is consistent, and you also put 1.1.2 to affects version/s as well. Could you raise a PR against 1.x branch as well? Cause it doesn't look like clean cherry picking. Please let me know if you don't have time to do so, I'll try to craft it. > Storm-hdfs tests are leaking resources > -- > > Key: STORM-2810 > URL: https://issues.apache.org/jira/browse/STORM-2810 > Project: Apache Storm > Issue Type: Bug > Components: storm-hdfs >Affects Versions: 2.0.0, 1.1.2 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The Storm-hdfs tests are leaking resources, and it seems to be making the > tests fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (STORM-2810) Storm-hdfs tests are leaking resources
[ https://issues.apache.org/jira/browse/STORM-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248995#comment-16248995 ] Jungtaek Lim commented on STORM-2810: - [~Srdo] Thanks, I merged the patch into master. I noticed the failure of storm-hdfs in Travis CI with OpenJDK7 is consistent, and you also put 1.1.2 to affects version/s as well. Could you raise a PR against 1.x branch as well? Cause it doesn't look like clean cherry picking. Please let me know if you don't have time to do so, I'll try to craft it. > Storm-hdfs tests are leaking resources > -- > > Key: STORM-2810 > URL: https://issues.apache.org/jira/browse/STORM-2810 > Project: Apache Storm > Issue Type: Bug > Components: storm-hdfs >Affects Versions: 2.0.0, 1.1.2 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The Storm-hdfs tests are leaking resources, and it seems to be making the > tests fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (STORM-2810) Storm-hdfs tests are leaking resources
[ https://issues.apache.org/jira/browse/STORM-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim reassigned STORM-2810: --- Assignee: Stig Rohde Døssing (was: Jungtaek Lim) > Storm-hdfs tests are leaking resources > -- > > Key: STORM-2810 > URL: https://issues.apache.org/jira/browse/STORM-2810 > Project: Apache Storm > Issue Type: Bug > Components: storm-hdfs >Affects Versions: 2.0.0, 1.1.2 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The Storm-hdfs tests are leaking resources, and it seems to be making the > tests fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (STORM-2810) Storm-hdfs tests are leaking resources
[ https://issues.apache.org/jira/browse/STORM-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-2810: Fix Version/s: 2.0.0 > Storm-hdfs tests are leaking resources > -- > > Key: STORM-2810 > URL: https://issues.apache.org/jira/browse/STORM-2810 > Project: Apache Storm > Issue Type: Bug > Components: storm-hdfs >Affects Versions: 2.0.0, 1.1.2 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The Storm-hdfs tests are leaking resources, and it seems to be making the > tests fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (STORM-2810) Storm-hdfs tests are leaking resources
[ https://issues.apache.org/jira/browse/STORM-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim reassigned STORM-2810: --- Assignee: Jungtaek Lim (was: Stig Rohde Døssing) > Storm-hdfs tests are leaking resources > -- > > Key: STORM-2810 > URL: https://issues.apache.org/jira/browse/STORM-2810 > Project: Apache Storm > Issue Type: Bug > Components: storm-hdfs >Affects Versions: 2.0.0, 1.1.2 >Reporter: Stig Rohde Døssing >Assignee: Jungtaek Lim > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The Storm-hdfs tests are leaking resources, and it seems to be making the > tests fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (STORM-2811) Nimbus may throw NPE if the same topology is killed multiple times, and the integration test kills the same topology multiple times
[
https://issues.apache.org/jira/browse/STORM-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated STORM-2811:
--
Labels: pull-request-available (was: )
> Nimbus may throw NPE if the same topology is killed multiple times, and the
> integration test kills the same topology multiple times
> ---
>
> Key: STORM-2811
> URL: https://issues.apache.org/jira/browse/STORM-2811
> Project: Apache Storm
> Issue Type: Bug
>Affects Versions: 2.0.0, 1.1.0
>Reporter: Stig Rohde Døssing
>Assignee: Stig Rohde Døssing
> Labels: pull-request-available
>
> {quote}
> 2017-11-12 08:45:50.353 o.a.s.d.n.Nimbus pool-14-thread-47 [WARN] Kill
> topology exception. (topology name='SlidingWindowTest-window20-slide10')
> java.lang.NullPointerException: null
> at
> org.apache.storm.cluster.IStormClusterState.getTopoId(IStormClusterState.java:171)
> ~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> at
> org.apache.storm.daemon.nimbus.Nimbus.tryReadTopoConfFromName(Nimbus.java:1970)
> ~[storm-server-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> at
> org.apache.storm.daemon.nimbus.Nimbus.killTopologyWithOpts(Nimbus.java:2760)
> ~[storm-server-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> at
> org.apache.storm.generated.Nimbus$Processor$killTopologyWithOpts.getResult(Nimbus.java:3226)
> ~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> at
> org.apache.storm.generated.Nimbus$Processor$killTopologyWithOpts.getResult(Nimbus.java:3210)
> ~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> ~[libthrift-0.10.0.jar:0.10.0]
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> ~[libthrift-0.10.0.jar:0.10.0]
> at
> org.apache.storm.security.auth.SimpleTransportPlugin$SimpleWrapProcessor.process(SimpleTransportPlugin.java:167)
> ~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> at
> org.apache.thrift.server.AbstractNonblockingServer$FrameBuffer.invoke(AbstractNonblockingServer.java:518)
> ~[libthrift-0.10.0.jar:0.10.0]
> at org.apache.thrift.server.Invocation.run(Invocation.java:18)
> ~[libthrift-0.10.0.jar:0.10.0]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [?:1.8.0_144]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [?:1.8.0_144]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (STORM-2811) Nimbus may throw NPE if the same topology is killed multiple times, and the integration test kills the same topology multiple times
Stig Rohde Døssing created STORM-2811:
-
Summary: Nimbus may throw NPE if the same topology is killed
multiple times, and the integration test kills the same topology multiple times
Key: STORM-2811
URL: https://issues.apache.org/jira/browse/STORM-2811
Project: Apache Storm
Issue Type: Bug
Affects Versions: 2.0.0, 1.1.0
Reporter: Stig Rohde Døssing
Assignee: Stig Rohde Døssing
{quote}
2017-11-12 08:45:50.353 o.a.s.d.n.Nimbus pool-14-thread-47 [WARN] Kill topology
exception. (topology name='SlidingWindowTest-window20-slide10')
java.lang.NullPointerException: null
at
org.apache.storm.cluster.IStormClusterState.getTopoId(IStormClusterState.java:171)
~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
at
org.apache.storm.daemon.nimbus.Nimbus.tryReadTopoConfFromName(Nimbus.java:1970)
~[storm-server-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
at
org.apache.storm.daemon.nimbus.Nimbus.killTopologyWithOpts(Nimbus.java:2760)
~[storm-server-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
at
org.apache.storm.generated.Nimbus$Processor$killTopologyWithOpts.getResult(Nimbus.java:3226)
~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
at
org.apache.storm.generated.Nimbus$Processor$killTopologyWithOpts.getResult(Nimbus.java:3210)
~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
~[libthrift-0.10.0.jar:0.10.0]
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
~[libthrift-0.10.0.jar:0.10.0]
at
org.apache.storm.security.auth.SimpleTransportPlugin$SimpleWrapProcessor.process(SimpleTransportPlugin.java:167)
~[storm-client-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
at
org.apache.thrift.server.AbstractNonblockingServer$FrameBuffer.invoke(AbstractNonblockingServer.java:518)
~[libthrift-0.10.0.jar:0.10.0]
at org.apache.thrift.server.Invocation.run(Invocation.java:18)
~[libthrift-0.10.0.jar:0.10.0]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[?:1.8.0_144]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[?:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
