You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by "S. Zhou" <my...@yahoo.com> on 2015/03/24 23:07:36 UTC
storm failed to activate topology
I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
We are using storm 0.8.0 on Ubuntu Lucid (10.04).
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
Exception in thread "main" NotAliveException(msg:MyTopology)
at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
at backtype.storm.command.activate$_main.invoke(activate.clj:7)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.activate.main(Unknown Source)
Re: storm failed to activate topology
Posted by "S. Zhou" <my...@yahoo.com>.
Thanks Derek. Yes, you are right. It turns out that there is another different physical machine running the nimbus as well. I killed it and it works.
On Wednesday, March 25, 2015 11:39 AM, Derek Dagit <de...@yahoo-inc.com> wrote:
Having a worker and nimbus on the same host should not be a problem.
We have seen this exact thing happen when two nimbus daemons are operating on the same file system location (sometimes an NFS mount).
The other thing that comes to mind is ZooKeeper configuration. Make sure all of the ZooKeeper hosts are part of the same ZooKeeper cluster.
--
Derek
________________________________
From: S. Zhou <my...@yahoo.com>
To: Derek Dagit <de...@yahoo-inc.com>
Cc: "user@storm.apache.org" <us...@storm.apache.org>
Sent: Wednesday, March 25, 2015 12:55 PM
Subject: Re: storm failed to activate topology
Only one nimbus is running. Another thing: I run nimbus and worker on the same machine using "distributed" mode. I am not sure if it could be an issue.
On Wednesday, March 25, 2015 10:13 AM, Derek Dagit <de...@yahoo-inc.com> wrote:
Check for a second nimbus process running somehow. There should be only one at a time.
--
Derek
________________________________
From: S. Zhou <my...@yahoo.com>
To: "user@storm.apache.org" <us...@storm.apache.org>; yuanjun Li <cs...@gmail.com>; S. Zhou <my...@yahoo.com>
Sent: Wednesday, March 25, 2015 12:03 PM
Subject: Re: storm failed to activate topology
Another thing I observed while investigating is:
when I run "storm jar" command, it creates a directory "Mytopology-2-1427302545" under "nimbus/stormdist". In that directory it has 3 files "stormcode.ser stormconf.ser stormjar.jar"
But after a while, these three files and the directory "Mytopology-2-1427302545" are disappeared. I tried to manually create that directory and copied back these three files, they are deleted (I guess by storm) again.
On Wednesday, March 25, 2015 7:52 AM, S. Zhou <my...@yahoo.com> wrote:
output from "storm list"
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
No topologies running.
On Tuesday, March 24, 2015 9:53 PM, yuanjun Li <cs...@gmail.com> wrote:
use ./storm list to list your top status.
2015-03-25 9:52 GMT+08:00 S. Zhou <my...@yahoo.com>:
I used "storm jar" first actually. Then the topology was active for a short period time then it dies. I checked log files from nimbus, ui, supervisor and worker and found no error message.
>
>
>
>
>
>On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com> wrote:
>
>
>
>Is the topology already running? Given the exception I suspect not. You will need to load it to the cluster using "storm jar ...". Activate should only be used if the topology is already loaded to the cluster and deactivated (i.e. spouts are not calling nextTuple).
>
>
>On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
>
>I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
>>
>>
>>We are using storm 0.8.0 on Ubuntu Lucid (10.04).
>>
>>
>>0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
>>Exception in thread "main" NotAliveException(msg:MyTopology)
>> at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
>> at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
>> at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
>> at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:622)
>> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
>> at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
>> at backtype.storm.command.activate$_main.invoke(activate.clj:7)
>> at clojure.lang.AFn.applyToHelper(AFn.java:161)
>> at clojure.lang.AFn.applyTo(AFn.java:151)
>> at backtype.storm.command.activate.main(Unknown Source)
>>
>>
>>
>
>
>
Re: storm failed to activate topology
Posted by Derek Dagit <de...@yahoo-inc.com>.
Having a worker and nimbus on the same host should not be a problem.
We have seen this exact thing happen when two nimbus daemons are operating on the same file system location (sometimes an NFS mount).
The other thing that comes to mind is ZooKeeper configuration. Make sure all of the ZooKeeper hosts are part of the same ZooKeeper cluster.
--
Derek
________________________________
From: S. Zhou <my...@yahoo.com>
To: Derek Dagit <de...@yahoo-inc.com>
Cc: "user@storm.apache.org" <us...@storm.apache.org>
Sent: Wednesday, March 25, 2015 12:55 PM
Subject: Re: storm failed to activate topology
Only one nimbus is running. Another thing: I run nimbus and worker on the same machine using "distributed" mode. I am not sure if it could be an issue.
On Wednesday, March 25, 2015 10:13 AM, Derek Dagit <de...@yahoo-inc.com> wrote:
Check for a second nimbus process running somehow. There should be only one at a time.
--
Derek
________________________________
From: S. Zhou <my...@yahoo.com>
To: "user@storm.apache.org" <us...@storm.apache.org>; yuanjun Li <cs...@gmail.com>; S. Zhou <my...@yahoo.com>
Sent: Wednesday, March 25, 2015 12:03 PM
Subject: Re: storm failed to activate topology
Another thing I observed while investigating is:
when I run "storm jar" command, it creates a directory "Mytopology-2-1427302545" under "nimbus/stormdist". In that directory it has 3 files "stormcode.ser stormconf.ser stormjar.jar"
But after a while, these three files and the directory "Mytopology-2-1427302545" are disappeared. I tried to manually create that directory and copied back these three files, they are deleted (I guess by storm) again.
On Wednesday, March 25, 2015 7:52 AM, S. Zhou <my...@yahoo.com> wrote:
output from "storm list"
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
No topologies running.
On Tuesday, March 24, 2015 9:53 PM, yuanjun Li <cs...@gmail.com> wrote:
use ./storm list to list your top status.
2015-03-25 9:52 GMT+08:00 S. Zhou <my...@yahoo.com>:
I used "storm jar" first actually. Then the topology was active for a short period time then it dies. I checked log files from nimbus, ui, supervisor and worker and found no error message.
>
>
>
>
>
>On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com> wrote:
>
>
>
>Is the topology already running? Given the exception I suspect not. You will need to load it to the cluster using "storm jar ...". Activate should only be used if the topology is already loaded to the cluster and deactivated (i.e. spouts are not calling nextTuple).
>
>
>On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
>
>I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
>>
>>
>>We are using storm 0.8.0 on Ubuntu Lucid (10.04).
>>
>>
>>0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
>>Exception in thread "main" NotAliveException(msg:MyTopology)
>> at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
>> at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
>> at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
>> at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:622)
>> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
>> at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
>> at backtype.storm.command.activate$_main.invoke(activate.clj:7)
>> at clojure.lang.AFn.applyToHelper(AFn.java:161)
>> at clojure.lang.AFn.applyTo(AFn.java:151)
>> at backtype.storm.command.activate.main(Unknown Source)
>>
>>
>>
>
>
>
Re: storm failed to activate topology
Posted by "S. Zhou" <my...@yahoo.com>.
Only one nimbus is running. Another thing: I run nimbus and worker on the same machine using "distributed" mode. I am not sure if it could be an issue.
On Wednesday, March 25, 2015 10:13 AM, Derek Dagit <de...@yahoo-inc.com> wrote:
Check for a second nimbus process running somehow. There should be only one at a time.
--
Derek
From: S. Zhou <my...@yahoo.com>
To: "user@storm.apache.org" <us...@storm.apache.org>; yuanjun Li <cs...@gmail.com>; S. Zhou <my...@yahoo.com>
Sent: Wednesday, March 25, 2015 12:03 PM
Subject: Re: storm failed to activate topology
Another thing I observed while investigating is:
when I run "storm jar" command, it creates a directory "Mytopology-2-1427302545" under "nimbus/stormdist". In that directory it has 3 files "stormcode.ser stormconf.ser stormjar.jar"
But after a while, these three files and the directory "Mytopology-2-1427302545" are disappeared. I tried to manually create that directory and copied back these three files, they are deleted (I guess by storm) again.
On Wednesday, March 25, 2015 7:52 AM, S. Zhou <my...@yahoo.com> wrote:
output from "storm list"0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627No topologies running.
On Tuesday, March 24, 2015 9:53 PM, yuanjun Li <cs...@gmail.com> wrote:
use ./storm list to list your top status.
2015-03-25 9:52 GMT+08:00 S. Zhou <my...@yahoo.com>:
I used "storm jar" first actually. Then the topology was active for a short period time then it dies. I checked log files from nimbus, ui, supervisor and worker and found no error message.
On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com> wrote:
Is the topology already running? Given the exception I suspect not. You will need to load it to the cluster using "storm jar ...". Activate should only be used if the topology is already loaded to the cluster and deactivated (i.e. spouts are not calling nextTuple).
On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
We are using storm 0.8.0 on Ubuntu Lucid (10.04).
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
Exception in thread "main" NotAliveException(msg:MyTopology)
at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
at backtype.storm.command.activate$_main.invoke(activate.clj:7)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.activate.main(Unknown Source)
Re: storm failed to activate topology
Posted by Derek Dagit <de...@yahoo-inc.com>.
Check for a second nimbus process running somehow. There should be only one at a time.
--
Derek
From: S. Zhou <my...@yahoo.com>
To: "user@storm.apache.org" <us...@storm.apache.org>; yuanjun Li <cs...@gmail.com>; S. Zhou <my...@yahoo.com>
Sent: Wednesday, March 25, 2015 12:03 PM
Subject: Re: storm failed to activate topology
Another thing I observed while investigating is:
when I run "storm jar" command, it creates a directory "Mytopology-2-1427302545" under "nimbus/stormdist". In that directory it has 3 files "stormcode.ser stormconf.ser stormjar.jar"
But after a while, these three files and the directory "Mytopology-2-1427302545" are disappeared. I tried to manually create that directory and copied back these three files, they are deleted (I guess by storm) again.
On Wednesday, March 25, 2015 7:52 AM, S. Zhou <my...@yahoo.com> wrote:
output from "storm list"0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627No topologies running.
On Tuesday, March 24, 2015 9:53 PM, yuanjun Li <cs...@gmail.com> wrote:
use ./storm list to list your top status.
2015-03-25 9:52 GMT+08:00 S. Zhou <my...@yahoo.com>:
I used "storm jar" first actually. Then the topology was active for a short period time then it dies. I checked log files from nimbus, ui, supervisor and worker and found no error message.
On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com> wrote:
Is the topology already running? Given the exception I suspect not. You will need to load it to the cluster using "storm jar ...". Activate should only be used if the topology is already loaded to the cluster and deactivated (i.e. spouts are not calling nextTuple).
On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
We are using storm 0.8.0 on Ubuntu Lucid (10.04).
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
Exception in thread "main" NotAliveException(msg:MyTopology)
at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
at backtype.storm.command.activate$_main.invoke(activate.clj:7)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.activate.main(Unknown Source)
Re: storm failed to activate topology
Posted by "S. Zhou" <my...@yahoo.com>.
Another thing I observed while investigating is:
when I run "storm jar" command, it creates a directory "Mytopology-2-1427302545" under "nimbus/stormdist". In that directory it has 3 files "stormcode.ser stormconf.ser stormjar.jar"
But after a while, these three files and the directory "Mytopology-2-1427302545" are disappeared. I tried to manually create that directory and copied back these three files, they are deleted (I guess by storm) again.
On Wednesday, March 25, 2015 7:52 AM, S. Zhou <my...@yahoo.com> wrote:
output from "storm list"0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627No topologies running.
On Tuesday, March 24, 2015 9:53 PM, yuanjun Li <cs...@gmail.com> wrote:
use ./storm list to list your top status.
2015-03-25 9:52 GMT+08:00 S. Zhou <my...@yahoo.com>:
I used "storm jar" first actually. Then the topology was active for a short period time then it dies. I checked log files from nimbus, ui, supervisor and worker and found no error message.
On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com> wrote:
Is the topology already running? Given the exception I suspect not. You will need to load it to the cluster using "storm jar ...". Activate should only be used if the topology is already loaded to the cluster and deactivated (i.e. spouts are not calling nextTuple).
On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
We are using storm 0.8.0 on Ubuntu Lucid (10.04).
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
Exception in thread "main" NotAliveException(msg:MyTopology)
at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
at backtype.storm.command.activate$_main.invoke(activate.clj:7)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.activate.main(Unknown Source)
Re: storm failed to activate topology
Posted by "S. Zhou" <my...@yahoo.com>.
output from "storm list"0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627No topologies running.
On Tuesday, March 24, 2015 9:53 PM, yuanjun Li <cs...@gmail.com> wrote:
use ./storm list to list your top status.
2015-03-25 9:52 GMT+08:00 S. Zhou <my...@yahoo.com>:
I used "storm jar" first actually. Then the topology was active for a short period time then it dies. I checked log files from nimbus, ui, supervisor and worker and found no error message.
On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com> wrote:
Is the topology already running? Given the exception I suspect not. You will need to load it to the cluster using "storm jar ...". Activate should only be used if the topology is already loaded to the cluster and deactivated (i.e. spouts are not calling nextTuple).
On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
We are using storm 0.8.0 on Ubuntu Lucid (10.04).
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
Exception in thread "main" NotAliveException(msg:MyTopology)
at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
at backtype.storm.command.activate$_main.invoke(activate.clj:7)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.activate.main(Unknown Source)
Re: storm failed to activate topology
Posted by yuanjun Li <cs...@gmail.com>.
use ./storm list to list your top status.
2015-03-25 9:52 GMT+08:00 S. Zhou <my...@yahoo.com>:
> I used "storm jar" first actually. Then the topology was active for a
> short period time then it dies. I checked log files from nimbus, ui,
> supervisor and worker and found no error message.
>
>
>
> On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com>
> wrote:
>
>
> Is the topology already running? Given the exception I suspect not. You
> will need to load it to the cluster using "storm jar ...". Activate should
> only be used if the topology is already loaded to the cluster and
> deactivated (i.e. spouts are not calling nextTuple).
>
> On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
>
> I was running this command "./storm activate MyTopology" and got the
> following exception. I looked through storm log files and could not see any
> clues. Any hints? Thanks!
>
> We are using storm 0.8.0 on Ubuntu Lucid (10.04).
>
> 0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at
> localhost:6627
> Exception in thread "main" NotAliveException(msg:MyTopology)
> at
> backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
> at
> org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
> at
> backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
> at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
> at backtype.storm.command.activate$_main.invoke(activate.clj:7)
> at clojure.lang.AFn.applyToHelper(AFn.java:161)
> at clojure.lang.AFn.applyTo(AFn.java:151)
> at backtype.storm.command.activate.main(Unknown Source)
>
>
>
>
>
Re: storm failed to activate topology
Posted by "S. Zhou" <my...@yahoo.com>.
I used "storm jar" first actually. Then the topology was active for a short period time then it dies. I checked log files from nimbus, ui, supervisor and worker and found no error message.
On Tuesday, March 24, 2015 5:43 PM, Nathan Leung <nc...@gmail.com> wrote:
Is the topology already running? Given the exception I suspect not. You will need to load it to the cluster using "storm jar ...". Activate should only be used if the topology is already loaded to the cluster and deactivated (i.e. spouts are not calling nextTuple).
On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
I was running this command "./storm activate MyTopology" and got the following exception. I looked through storm log files and could not see any clues. Any hints? Thanks!
We are using storm 0.8.0 on Ubuntu Lucid (10.04).
0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at localhost:6627
Exception in thread "main" NotAliveException(msg:MyTopology)
at backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
at org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
at backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
at backtype.storm.command.activate$_main.invoke(activate.clj:7)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.AFn.applyTo(AFn.java:151)
at backtype.storm.command.activate.main(Unknown Source)
Re: storm failed to activate topology
Posted by Nathan Leung <nc...@gmail.com>.
Is the topology already running? Given the exception I suspect not. You
will need to load it to the cluster using "storm jar ...". Activate should
only be used if the topology is already loaded to the cluster and
deactivated (i.e. spouts are not calling nextTuple).
On Tue, Mar 24, 2015 at 6:07 PM, S. Zhou <my...@yahoo.com> wrote:
> I was running this command "./storm activate MyTopology" and got the
> following exception. I looked through storm log files and could not see any
> clues. Any hints? Thanks!
>
> We are using storm 0.8.0 on Ubuntu Lucid (10.04).
>
> 0 [main] INFO backtype.storm.thrift - Connecting to Nimbus at
> localhost:6627
> Exception in thread "main" NotAliveException(msg:MyTopology)
> at
> backtype.storm.generated.Nimbus$activate_result.read(Nimbus.java:4188)
> at
> org.apache.thrift7.TServiceClient.receiveBase(TServiceClient.java:78)
> at
> backtype.storm.generated.Nimbus$Client.recv_activate(Nimbus.java:210)
> at backtype.storm.generated.Nimbus$Client.activate(Nimbus.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
> at backtype.storm.command.activate$_main.invoke(activate.clj:7)
> at clojure.lang.AFn.applyToHelper(AFn.java:161)
> at clojure.lang.AFn.applyTo(AFn.java:151)
> at backtype.storm.command.activate.main(Unknown Source)
>
>