nimbus Thrift service b0rken, ui gets 500

135 views

Skip to first unread message

Chip Salzenberg

unread,

Jan 5, 2012, 11:27:42 PM1/5/12

to storm-user

I figured out how to deploy the ExclamationTopology to a one-server
storm daemon, which is great. And it ran until I stopped it, which is
great. But using the UI I can't ask for information about the
topology, whether it's running or not. The ui is getting an EOF on
read, and the below is in the nimbus log. Help?

2012-01-05 20:24:30 TNonblockingServer [ERROR] Unexpected exception
while invoking!
java.lang.RuntimeException: java.lang.NullPointerException
at clojure.lang.LazySeq.sval(LazySeq.java:47)
at clojure.lang.LazySeq.seq(LazySeq.java:56)
at clojure.lang.RT.seq(RT.java:450)
at clojure.core$seq.invoke(core.clj:122)
at clojure.core$dorun.invoke(core.clj:2450)
at clojure.core$doall.invoke(core.clj:2465)
at backtype.storm.daemon.nimbus$fn__2853$exec_fn__977__auto__
$reify__2869.getTopologyInfo(nimbus.clj:794)
at backtype.storm.generated.Nimbus$Processor
$getTopologyInfo.getResult(Nimbus.java:1240)
at backtype.storm.generated.Nimbus$Processor
$getTopologyInfo.getResult(Nimbus.java:1228)
at
org.apache.thrift7.ProcessFunction.process(ProcessFunction.java:32)
at
org.apache.thrift7.TBaseProcessor.process(TBaseProcessor.java:34)
at org.apache.thrift7.server.TNonblockingServer
$FrameBuffer.invoke(TNonblockingServer.java:632)
at org.apache.thrift7.server.THsHaServer
$Invocation.run(THsHaServer.java:201)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at backtype.storm.daemon.nimbus$fn__2853$exec_fn__977__auto__
$reify__2869$iter__2910__2914$fn__2915.invoke(nimbus.clj:802)
at clojure.lang.LazySeq.sval(LazySeq.java:42)
... 15 more

Nathan Marz

unread,

Jan 6, 2012, 1:59:37 AM1/6/12

to storm...@googlegroups.com

Chip and I resolved this on IRC. The underlying issue was that there were no supervisors in the cluster, so the tasks for the topology couldn't be assigned anywhere. This was causing issues for the Storm UI, and there's now a ticket open for this edge case: https://github.com/nathanmarz/storm/issues/92