date:20151107

Re: KafkaSpout starts from 0 after restart

2015-11-07 Thread Jaime Solano

The offset should be under the zkroot. zkroot is not a local path per se,
but a logical path in zookeeper. That's why you should use zookeeper cli to
view its contents.
-Jaime
On Nov 7, 2015 2:26 AM, "Birendra Kumar Singh"  wrote:

> Thanks Jaime - That worked
> However, I am still not able to locate the files within the zookeeper that
> stores the offset information.
> Would be of great help  if I can locate those
>
> On Sat, Nov 7, 2015 at 4:24 AM, Jaime Solano  wrote:
>
>> Hi Birendra,
>>
>> What type of bolts are you using in your topology? If your extending from
>> BaseRichBolt, you have to explicitily ack the tuples, otherwise your
>> KafkaSpout will try to consume them again after 30 secs.
>>
>> -Jaime
>> On Nov 6, 2015 5:38 PM, "Birendra Kumar Singh" 
>> wrote:
>>
>>> In fact, what I see is that once all messages are being consumed - it
>>> starts consuming again all of them from the beginning..
>>>
>>> On Sat, Nov 7, 2015 at 3:49 AM, Birendra Kumar Singh >> > wrote:
>>>
 Can you guys please help me understand how to zk for existence of
 offset.
 I tried this on a separate zkroot as well, but the problem still
 persists.

 Thanks
 Birendra

 On Fri, Nov 6, 2015 at 11:08 PM, Santosh Pingale <
 pingalesant...@gmail.com> wrote:

> To add to Stephen's answer, you might want to change your zkroot from
> /broker to something else as Kafka uses it to maintain the metadata.
>
> Nevertheless, you will need to check zk for existence of offset and
> not local directories of Kafka cluster.
>


>>>
>

Store previous calculated result

2015-11-07 Thread Miguel Ángel Fernández Fernández

In a trident scenario, a realtime operation needs to know the previous
calculated result.

My current solution is very poor and probably incorrect (a hashmap in
bolts). Now I'm thinking to incorporate a cache (redis, memcached ...)

However, I *suppose*  that
there is a standard solution for this problem in Trident (maybe a special
state).

What do you think is the best approach?

Thanks for your time

Re: Error on initialization

2015-11-07 Thread researcher cs

this happened when submitted topology

On Sat, Nov 7, 2015 at 4:09 PM, researcher cs 
wrote:

>
>
>
>
>
>
>
>
>
> *here what i got in worker log file [ERROR] Error on initialization of
> server mk-worker org.apache.storm.netty.channel.ChannelException: Failed to
> bind to: 0.0.0.0/0.0.0.0:6703  at
> org.apache.storm.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
> ~[storm-core-0.9.5.jar:0.9.5] at
> backtype.storm.messaging.netty.Server.(Server.java:130)
> ~[storm-core-0.9.5.jar:0.9.5] at
> backtype.storm.messaging.netty.Context.bind(Context.java:75)
> ~[storm-core-0.9.5.jar:0.9.5] at
> backtype.storm.messaging.loader$launch_receive_thread_BANG_.doInvoke(loader.clj:68)
> ~[storm-core-0.9.5.jar:0.9.5] at
> clojure.lang.RestFn.invoke(RestFn.java:668) [clojure-1.5.1.jar:na] at
> backtype.storm.daemon.worker$launch_receive_thread.invoke(worker.clj:378)
> ~[storm-core-0.9.5.jar:0.9.5] at
> backtype.storm.daemon.worker$fn__6959$exec_fn__1103__auto6960.invoke(worker.clj:413)
> ~[storm-core-0.9.5.jar:0.9.5] at
> clojure.lang.AFn.applyToHelper(AFn.java:185) [clojure-1.5.1.jar:na] at
> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
> clojure.core$apply.invoke(core.clj:617) ~[clojure-1.5.1.jar:na] at
> backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
> [clojure-1.5.1.jar:na] at
> backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
> [storm-core-0.9.5.jar:0.9.5] at
> clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
> backtype.storm.daemon.worker.main(Unknown Source)
> [storm-core-0.9.5.jar:0.9.5] java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method) ~[na:1.6.0_38] at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124)
> ~[na:1.6.0_38] at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> ~[na:1.6.0_38] at
> org.apache.storm.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
> ~[storm-core-0.9.5.jar:0.9.5] at
> org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
> ~[storm-core-0.9.5.jar:0.9.5] at
> org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
> ~[storm-core-0.9.5.jar:0.9.5] at
> org.apache.storm.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
> ~[storm-core-0.9.5.jar:0.9.5] at
> org.apache.storm.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
> ~[storm-core-0.9.5.jar:0.9.5] at
> org.apache.storm.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
> ~[storm-core-0.9.5.jar:0.9.5] at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> ~[na:1.6.0_38] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> ~[na:1.6.0_38] at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_38]and
> this when executed the command that launch supervisor and worker  cause of
> supervisor still hasn't start *
>
>
>
> *[ERROR] Halting process: ("Error on initialization")
> java.lang.RuntimeException: ("Error on initialization") at
> backtype.storm.util$exit_process_BANG_.doInvoke(util.clj:325)
> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:423)
> [clojure-1.5.1.jar:na] at
> backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
> [clojure-1.5.1.jar:na] at
> backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
> [storm-core-0.9.5.jar:0.9.5] at
> clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
> backtype.storm.daemon.worker.main(Unknown Source)
> [storm-core-0.9.5.jar:0.9.5]*
>
> *storm version 0.9.5 *
>
> *zookeeper -3.4.6 *
>

Error on initialization

2015-11-07 Thread researcher cs

*here what i got in worker log file [ERROR] Error on initialization of
server mk-worker org.apache.storm.netty.channel.ChannelException: Failed to
bind to: 0.0.0.0/0.0.0.0:6703  at
org.apache.storm.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
~[storm-core-0.9.5.jar:0.9.5] at
backtype.storm.messaging.netty.Server.(Server.java:130)
~[storm-core-0.9.5.jar:0.9.5] at
backtype.storm.messaging.netty.Context.bind(Context.java:75)
~[storm-core-0.9.5.jar:0.9.5] at
backtype.storm.messaging.loader$launch_receive_thread_BANG_.doInvoke(loader.clj:68)
~[storm-core-0.9.5.jar:0.9.5] at
clojure.lang.RestFn.invoke(RestFn.java:668) [clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker$launch_receive_thread.invoke(worker.clj:378)
~[storm-core-0.9.5.jar:0.9.5] at
backtype.storm.daemon.worker$fn__6959$exec_fn__1103__auto6960.invoke(worker.clj:413)
~[storm-core-0.9.5.jar:0.9.5] at
clojure.lang.AFn.applyToHelper(AFn.java:185) [clojure-1.5.1.jar:na] at
clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
clojure.core$apply.invoke(core.clj:617) ~[clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
[storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
[clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
[storm-core-0.9.5.jar:0.9.5] at
clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker.main(Unknown Source)
[storm-core-0.9.5.jar:0.9.5] java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method) ~[na:1.6.0_38] at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124)
~[na:1.6.0_38] at
sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
~[na:1.6.0_38] at
org.apache.storm.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
~[storm-core-0.9.5.jar:0.9.5] at
org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
~[storm-core-0.9.5.jar:0.9.5] at
org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
~[storm-core-0.9.5.jar:0.9.5] at
org.apache.storm.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
~[storm-core-0.9.5.jar:0.9.5] at
org.apache.storm.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
~[storm-core-0.9.5.jar:0.9.5] at
org.apache.storm.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
~[storm-core-0.9.5.jar:0.9.5] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
~[na:1.6.0_38] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
~[na:1.6.0_38] at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_38]and
this when executed the command that launch supervisor and worker  cause of
supervisor still hasn't start *



*[ERROR] Halting process: ("Error on initialization")
java.lang.RuntimeException: ("Error on initialization") at
backtype.storm.util$exit_process_BANG_.doInvoke(util.clj:325)
[storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:423)
[clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
[storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
[clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
[storm-core-0.9.5.jar:0.9.5] at
clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker.main(Unknown Source)
[storm-core-0.9.5.jar:0.9.5]*

*storm version 0.9.5 *

*zookeeper -3.4.6 *

Re: Error on initialization

2015-11-07 Thread researcher cs

sorry i'm new to storm
is this command that check !?
ps -ef|grep 67xx

On Sat, Nov 7, 2015 at 4:17 PM, Nick R. Katsipoulakis  wrote:

> Hello,
>
> It seems that port 6703 can not be binded for the worker. Are you sure
> that this port is not used by another process?
>
> Nick
>
> On Sat, Nov 7, 2015 at 7:10 PM, researcher cs 
> wrote:
>
>> this happened when submitted topology
>>
>> On Sat, Nov 7, 2015 at 4:09 PM, researcher cs 
>> wrote:
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *here what i got in worker log file [ERROR] Error on initialization of
>>> server mk-worker org.apache.storm.netty.channel.ChannelException: Failed to
>>> bind to: 0.0.0.0/0.0.0.0:6703  at
>>> org.apache.storm.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> backtype.storm.messaging.netty.Server.(Server.java:130)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> backtype.storm.messaging.netty.Context.bind(Context.java:75)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> backtype.storm.messaging.loader$launch_receive_thread_BANG_.doInvoke(loader.clj:68)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> clojure.lang.RestFn.invoke(RestFn.java:668) [clojure-1.5.1.jar:na] at
>>> backtype.storm.daemon.worker$launch_receive_thread.invoke(worker.clj:378)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> backtype.storm.daemon.worker$fn__6959$exec_fn__1103__auto6960.invoke(worker.clj:413)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> clojure.lang.AFn.applyToHelper(AFn.java:185) [clojure-1.5.1.jar:na] at
>>> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
>>> clojure.core$apply.invoke(core.clj:617) ~[clojure-1.5.1.jar:na] at
>>> backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
>>> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
>>> [clojure-1.5.1.jar:na] at
>>> backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
>>> [storm-core-0.9.5.jar:0.9.5] at
>>> clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
>>> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
>>> backtype.storm.daemon.worker.main(Unknown Source)
>>> [storm-core-0.9.5.jar:0.9.5] java.net.BindException: Address already in use
>>> at sun.nio.ch.Net.bind(Native Method) ~[na:1.6.0_38] at
>>> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124)
>>> ~[na:1.6.0_38] at
>>> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>>> ~[na:1.6.0_38] at
>>> org.apache.storm.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> org.apache.storm.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> org.apache.storm.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> org.apache.storm.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
>>> ~[storm-core-0.9.5.jar:0.9.5] at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>> ~[na:1.6.0_38] at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>> ~[na:1.6.0_38] at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_38]and
>>> this when executed the command that launch supervisor and worker  cause of
>>> supervisor still hasn't start *
>>>
>>>
>>>
>>> *[ERROR] Halting process: ("Error on initialization")
>>> java.lang.RuntimeException: ("Error on initialization") at
>>> backtype.storm.util$exit_process_BANG_.doInvoke(util.clj:325)
>>> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:423)
>>> [clojure-1.5.1.jar:na] at
>>> backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
>>> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
>>> [clojure-1.5.1.jar:na] at
>>> backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
>>> [storm-core-0.9.5.jar:0.9.5] at
>>> clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
>>> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
>>> backtype.storm.daemon.worker.main(Unknown Source)
>>> [storm-core-0.9.5.jar:0.9.5]*
>>>
>>> *storm version 0.9.5 *
>>>
>>> *zookeeper -3.4.6 *
>>>
>>
>>
>
>
> --
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh
>

Re: Error on initialization

2015-11-07 Thread researcher cs

i tried to run
username@ubuntu:~$ sudo netstat -antlp|grep 2181
tcp6 0 0 :::2181 :::* LISTEN 2301/java
tcp6 0 0 127.0.0.1:2181 127.0.0.1:65107 ESTABLISHED 2301/java
tcp6 0 0 127.0.0.1:2181 127.0.0.1:65105 ESTABLISHED 2301/java
tcp6 0 0 127.0.0.1:65110 127.0.0.1:2181 ESTABLISHED 2512/java
tcp6 0 0 127.0.0.1:65122 127.0.0.1:2181 ESTABLISHED 2963/java
tcp6 0 0 127.0.0.1:65107 127.0.0.1:2181 ESTABLISHED 2415/java
tcp6 0 0 127.0.0.1:2181 127.0.0.1:65110 ESTABLISHED 2301/java
tcp6 0 0 127.0.0.1:65105 127.0.0.1:2181 ESTABLISHED 2319/java
tcp6 0 0 127.0.0.1:2181 127.0.0.1:65122 ESTABLISHED 2301/java



On Sat, Nov 7, 2015 at 5:40 PM, researcher cs 
wrote:

> ok i tried to run this "sudo netstat -antlp|grep 6703" and got this
> tcp6 0 0 :::6703 :::* LISTEN 2963/java
>
> here did you mean the pid is 2963 if that i got nothing when ran
> sudo ps -ef|grep 2963
>
>
>
>
> On Sat, Nov 7, 2015 at 5:21 PM, Fan Jiang  wrote:
>
>> Type in "sudo netstat -antlp|grep 6703" to see if it returns anything -
>> it should in your case. The rightmost column in the result is the PID of
>> the running process using the port. The you can type in "sudo ps -ef|grep
>> " to see what the exact process is. Make sure you prefix the commands
>> with "sudo" so that you can search among all processes running on the
>> machine.
>>
>> Please be nice to others who answer your question nicely. Nobody owe you
>> an answer.
>>
>> —
>> Sincerely,
>> Fan Jiang
>>
>>
>> On Sat, Nov 7, 2015 at 8:07 PM, Nick R. Katsipoulakis <
>> nick.kat...@gmail.com> wrote:
>>
>>> Then I guess it means that another process is using port 6703. That
>>> means that the supervisor (Storm) can not start worker process on port 6703
>>> and that is why you get the previous error.
>>>
>>> I hope the above helps.
>>>
>>> Nick
>>>
>>> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs >> > wrote:
>>>
 sorry this command ps -ef|grep 6703 got this result username 3299 2766
 0 02:55 pts/7 00:00:00 grep --color=auto 6703

 On Sat, Nov 7, 2015 at 4:57 PM, researcher cs <
 prog.researc...@gmail.com> wrote:

> i used this command ps -ef|grep 6703 and got this username 4162 3449 0
> 02:32 pts/8 00:00:00 grep --color=auto 6703
>
> and this command  netstat -netulp | grep 2181 and got this
>  (Not all processes could be identified, non-owned process info will
> not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
> :::* LISTEN 1000 14805 2301/java
>


>>>
>>>
>>> --
>>> Nick R. Katsipoulakis,
>>> Department of Computer Science
>>> University of Pittsburgh
>>>
>>
>>
>

Re: Need help in this problem " Address already in use(0x62)"

2015-11-07 Thread researcher cs

i upgraded the version to storm -0.9.5 and got in supervisor log file that
it hasn't start still but i executed tha commend that launch between
supervisor and worker and got this
[ERROR] Halting process: ("Error on initialization")
java.lang.RuntimeException: ("Error on initialization") at
backtype.storm.util$exit_process_BANG_.doInvoke(util.clj:325)
[storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:423)
[clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
[storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
[clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
[storm-core-0.9.5.jar:0.9.5] at
clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
backtype.storm.daemon.worker.main(Unknown Source)
[storm-core-0.9.5.jar:0.9.5]

On Tue, Nov 3, 2015 at 8:36 AM, researcher cs 
wrote:

> i tried this command  ps -ef|grep 6703  and got this
>
> st 2991 2595 41 14:51 pts/3 00:05:19 java -server -Xmx768m
> -Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib
> -Dlogfile.name=worker-6703.log -Dstorm.home=/home/st/storm-0.8.2
> -Dlog4j.configuration=storm.log.properties -cp
> /home/st/storm-0.8.2/storm-0.8.2.jar:/home/st/storm-0.8.2/lib/curator-client-1.0.1.jar:/home/st/storm-0.8.2/lib/zookeeper-3.4.5.jar:/home/st/storm-0.8.2/lib/objenesis-1.2.jar:/home/st/storm-0.8.2/lib/disruptor-2.10.1.jar:/home/st/storm-0.8.2/lib/servlet-api-2.5-20081211.jar:/home/st/storm-0.8.2/lib/ring-core-1.1.5.jar:/home/st/storm-0.8.2/lib/tools.logging-0.2.3.jar:/home/st/storm-0.8.2/lib/libthrift7-0.7.0.jar:/home/st/storm-0.8.2/lib/slf4j-api-1.5.8.jar:/home/st/storm-0.8.2/lib/hiccup-0.3.6.jar:/home/st/storm-0.8.2/lib/guava-13.0.jar:/home/st/storm-0.8.2/lib/junit-3.8.1.jar:/home/st/storm-0.8.2/lib/servlet-api-2.5.jar:/home/st/storm-0.8.2/lib/reflectasm-1.07-shaded.jar:/home/st/storm-0.8.2/lib/zookeeper-3.3.3.jar:/home/st/storm-0.8.2/lib/jzmq-2.1.0.jar:/home/st/storm-0.8.2/lib/jgrapht-0.8.3.jar:/home/st/storm-0.8.2/lib/httpclient-4.1.1.jar:/home/st/storm-0.8.2/lib/clojure-1.4.0.jar:/home/st/storm-0.8.2/lib/clout-1.0.1.jar:/home/st/storm-0.8.2/lib/core.incubator-0.1.0.jar:/home/st/storm-0.8.2/lib/ring-jetty-adapter-0.3.11.jar:/home/st/storm-0.8.2/lib/asm-4.0.jar:/home/st/storm-0.8.2/lib/commons-io-1.4.jar:/home/st/storm-0.8.2/lib/snakeyaml-1.9.jar:/home/st/storm-0.8.2/lib/slf4j-log4j12-1.5.8.jar:/home/st/storm-0.8.2/lib/tools.cli-0.2.2.jar:/home/st/storm-0.8.2/lib/commons-fileupload-1.2.1.jar:/home/st/storm-0.8.2/lib/commons-exec-1.1.jar:/home/st/storm-0.8.2/lib/minlog-1.2.jar:/home/st/storm-0.8.2/lib/ring-servlet-0.3.11.jar:/home/st/storm-0.8.2/lib/carbonite-1.5.0.jar:/home/st/storm-0.8.2/lib/clj-time-0.4.1.jar:/home/st/storm-0.8.2/lib/jetty-util-6.1.26.jar:/home/st/storm-0.8.2/lib/tools.macro-0.1.0.jar:/home/st/storm-0.8.2/lib/commons-codec-1.4.jar:/home/st/storm-0.8.2/lib/commons-logging-1.1.1.jar:/home/st/storm-0.8.2/lib/jetty-6.1.26.jar:/home/st/storm-0.8.2/lib/jline-0.9.94.jar:/home/st/storm-0.8.2/lib/json-simple-1.1.jar:/home/st/storm-0.8.2/lib/kryo-2.17.jar:/home/st/storm-0.8.2/lib/math.numeric-tower-0.0.1.jar:/home/st/storm-0.8.2/lib/compojure-1.1.3.jar:/home/st/storm-0.8.2/lib/httpcore-4.1.jar:/home/st/storm-0.8.2/lib/commons-lang-2.5.jar:/home/st/storm-0.8.2/lib/log4j-1.2.16.jar:/home/st/storm-0.8.2/lib/joda-time-2.0.jar:/home/st/storm-0.8.2/lib/curator-framework-1.0.1.jar:/home/st/storm-0.8.2/log4j:/home/st/storm-0.8.2/conf:/tmp/storm/supervisor/stormdist/fsd-1-1446555065/stormjar.jar
> backtype.storm.daemon.worker fsd-1-1446555065
> 3e3092ff-2722-400a-8aa9-362c9144a6fe 6703
> 0f68434a-d2f8-41c3-8d1b-9b0d0f2fcb6a st 3434 3217 2 15:04 pts/8 00:00:00
> grep --color=auto 6703
>
> and tried to change ip_local_port_range as you said but problem still
> so i'll try to upgrade the version but is there any other solution ?
>
> On Mon, Nov 2, 2015 at 2:40 PM, researcher cs 
> wrote:
>
>> many many many thanks for replying and helping , i'll try what you said ,
>> But the coder of the project that i used it , he used old version 0.8.2 so
>> i'm trying first to use it then upgrade the version
>>
>> On Mon, Nov 2, 2015 at 1:59 PM, Feng Longda  wrote:
>>
>>> I have resolved this problem several times.
>>>
>>> There are two root cause.
>>> (1) local temporary network ports are conflict with storm's ports.
>>> (2) the old worker failed to be killed when kill topology.
>>>
>>> Firstly, please do "ps -ef|grep 67xx" to check whether it is due to the
>>> second problem. if there is no worker using the port. it would be temporary
>>> port conflict.
>>> please do the following action with root privilege
>>>
>>> echo 'net.ipv4.ip_local_port_range = 10240 65535' >> /etc/sysctl.conf
>>> /sbin/sysctl -p
>>>
>>> why occur this, due to in every network connection,  client

Re: Error on initialization

2015-11-07 Thread Nick R. Katsipoulakis

Hello,

Checking if a port is used is not a Storm thing. It has to do with the
processes currently running on your Server. Also, checking on the currently
used ports relies on the OS you are using. I am sure if you Google how to
get the used ports for your OS you will find many solutions.

Cheers,
Nick

On Sat, Nov 7, 2015 at 7:34 PM, researcher cs 
wrote:

> sorry i'm new to storm
> is this command that check !?
> ps -ef|grep 67xx
>
> On Sat, Nov 7, 2015 at 4:17 PM, Nick R. Katsipoulakis <
> nick.kat...@gmail.com> wrote:
>
>> Hello,
>>
>> It seems that port 6703 can not be binded for the worker. Are you sure
>> that this port is not used by another process?
>>
>> Nick
>>
>> On Sat, Nov 7, 2015 at 7:10 PM, researcher cs 
>> wrote:
>>
>>> this happened when submitted topology
>>>
>>> On Sat, Nov 7, 2015 at 4:09 PM, researcher cs >> > wrote:
>>>









 *here what i got in worker log file [ERROR] Error on initialization of
 server mk-worker org.apache.storm.netty.channel.ChannelException: Failed to
 bind to: 0.0.0.0/0.0.0.0:6703  at
 org.apache.storm.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
 ~[storm-core-0.9.5.jar:0.9.5] at
 backtype.storm.messaging.netty.Server.(Server.java:130)
 ~[storm-core-0.9.5.jar:0.9.5] at
 backtype.storm.messaging.netty.Context.bind(Context.java:75)
 ~[storm-core-0.9.5.jar:0.9.5] at
 backtype.storm.messaging.loader$launch_receive_thread_BANG_.doInvoke(loader.clj:68)
 ~[storm-core-0.9.5.jar:0.9.5] at
 clojure.lang.RestFn.invoke(RestFn.java:668) [clojure-1.5.1.jar:na] at
 backtype.storm.daemon.worker$launch_receive_thread.invoke(worker.clj:378)
 ~[storm-core-0.9.5.jar:0.9.5] at
 backtype.storm.daemon.worker$fn__6959$exec_fn__1103__auto6960.invoke(worker.clj:413)
 ~[storm-core-0.9.5.jar:0.9.5] at
 clojure.lang.AFn.applyToHelper(AFn.java:185) [clojure-1.5.1.jar:na] at
 clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
 clojure.core$apply.invoke(core.clj:617) ~[clojure-1.5.1.jar:na] at
 backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
 [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
 [clojure-1.5.1.jar:na] at
 backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
 [storm-core-0.9.5.jar:0.9.5] at
 clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
 clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
 backtype.storm.daemon.worker.main(Unknown Source)
 [storm-core-0.9.5.jar:0.9.5] java.net.BindException: Address already in use
 at sun.nio.ch.Net.bind(Native Method) ~[na:1.6.0_38] at
 sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124)
 ~[na:1.6.0_38] at
 sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
 ~[na:1.6.0_38] at
 org.apache.storm.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
 ~[storm-core-0.9.5.jar:0.9.5] at
 org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
 ~[storm-core-0.9.5.jar:0.9.5] at
 org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
 ~[storm-core-0.9.5.jar:0.9.5] at
 org.apache.storm.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
 ~[storm-core-0.9.5.jar:0.9.5] at
 org.apache.storm.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
 ~[storm-core-0.9.5.jar:0.9.5] at
 org.apache.storm.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
 ~[storm-core-0.9.5.jar:0.9.5] at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 ~[na:1.6.0_38] at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 ~[na:1.6.0_38] at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_38]and
 this when executed the command that launch supervisor and worker  cause of
 supervisor still hasn't start *



 *[ERROR] Halting process: ("Error on initialization")
 java.lang.RuntimeException: ("Error on initialization") at
 backtype.storm.util$exit_process_BANG_.doInvoke(util.clj:325)
 [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:423)
 [clojure-1.5.1.jar:na] at
 backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
 [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
 [clojure-1.5.1.jar:na] at
 backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
 [storm-core-0.9.5.jar:0.9.5] at
 clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
 clojure.lang.AFn.applyTo(AFn.java:151)

Re: Error on initialization

2015-11-07 Thread researcher cs

sorry this command ps -ef|grep 6703 got this result username 3299 2766 0
02:55 pts/7 00:00:00 grep --color=auto 6703

On Sat, Nov 7, 2015 at 4:57 PM, researcher cs 
wrote:

> i used this command ps -ef|grep 6703 and got this username 4162 3449 0
> 02:32 pts/8 00:00:00 grep --color=auto 6703
>
> and this command  netstat -netulp | grep 2181 and got this
>  (Not all processes could be identified, non-owned process info will not
> be shown, you would have to be root to see it all.) tcp6 0 0 :::2181 :::*
> LISTEN 1000 14805 2301/java
>

Re: Error on initialization

2015-11-07 Thread researcher cs

 i used this command ps -ef|grep 6703 and got this username 4162 3449 0
02:32 pts/8 00:00:00 grep --color=auto 6703

and this command  netstat -netulp | grep 2181 and got this
 (Not all processes could be identified, non-owned process info will not be
shown, you would have to be root to see it all.) tcp6 0 0 :::2181 :::*
LISTEN 1000 14805 2301/java

Re: Error on initialization

2015-11-07 Thread Nick R. Katsipoulakis

Well, if that is the case then that means that another worker process is
already active. You have to go through the supervisor.log to see if Storm
has another worker process running.

Nick

On Sat, Nov 7, 2015 at 8:09 PM, researcher cs 
wrote:

> sorry how do you know if that any other process using port 6703 ?! i'm now
> running storm and think that this process for it ! am i right or wrong ?
>
> 3299 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>
> On Sat, Nov 7, 2015 at 5:06 PM, Nick R. Katsipoulakis <
> nick.kat...@gmail.com> wrote:
>
>> Then I guess it means that another process is using port 6703. That means
>> that the supervisor (Storm) can not start worker process on port 6703 and
>> that is why you get the previous error.
>>
>> I hope the above helps.
>>
>> Nick
>>
>> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs 
>> wrote:
>>
>>> sorry this command ps -ef|grep 6703 got this result username 3299 2766
>>> 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>>>
>>> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs >> > wrote:
>>>
 i used this command ps -ef|grep 6703 and got this username 4162 3449 0
 02:32 pts/8 00:00:00 grep --color=auto 6703

 and this command  netstat -netulp | grep 2181 and got this
  (Not all processes could be identified, non-owned process info will
 not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
 :::* LISTEN 1000 14805 2301/java

>>>
>>>
>>
>>
>> --
>> Nick R. Katsipoulakis,
>> Department of Computer Science
>> University of Pittsburgh
>>
>
>


-- 
Nick R. Katsipoulakis,
Department of Computer Science
University of Pittsburgh

Re: Error on initialization

2015-11-07 Thread researcher cs

i'm now asking you about the result of the command of
ps -ef|grep 6703 got this result username 3299 2766 0 02:55 pts/7 00:00:00
grep --color=auto 6703

you said
"
Then I guess it means that another process is using port 6703. That means
that the supervisor (Storm) can not start worker process on p
ort 6703 and that is why you get the previous error.
" i got that you guess from the result of the command !

On Sat, Nov 7, 2015 at 5:21 PM, Nick R. Katsipoulakis  wrote:

> Hello again,
>
> Because the error you posted has the following:
>
> *[ERROR] Error on initialization of server mk-worker
> org.apache.storm.netty.channel.ChannelException: Failed to bind
> to: 0.0.0.0/0.0.0.0:6703 *
>
> If that is not the ERROR then you should post the proper part of your log.
>
> Nick
>
> On Sat, Nov 7, 2015 at 8:17 PM, researcher cs 
> wrote:
>
>> i'm just asking why you guess that there are another process using port
>> 6703 ?!!!
>> and my supervisor using one worker only
>>
>> On Sat, Nov 7, 2015 at 5:13 PM, Nick R. Katsipoulakis <
>> nick.kat...@gmail.com> wrote:
>>
>>> Well, if that is the case then that means that another worker process is
>>> already active. You have to go through the supervisor.log to see if Storm
>>> has another worker process running.
>>>
>>> Nick
>>>
>>> On Sat, Nov 7, 2015 at 8:09 PM, researcher cs >> > wrote:
>>>
 sorry how do you know if that any other process using port 6703 ?! i'm
 now running storm and think that this process for it ! am i right or wrong 
 ?

 3299 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703

 On Sat, Nov 7, 2015 at 5:06 PM, Nick R. Katsipoulakis <
 nick.kat...@gmail.com> wrote:

> Then I guess it means that another process is using port 6703. That
> means that the supervisor (Storm) can not start worker process on port 
> 6703
> and that is why you get the previous error.
>
> I hope the above helps.
>
> Nick
>
> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs <
> prog.researc...@gmail.com> wrote:
>
>> sorry this command ps -ef|grep 6703 got this result username 3299
>> 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>>
>> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs <
>> prog.researc...@gmail.com> wrote:
>>
>>> i used this command ps -ef|grep 6703 and got this username 4162 3449
>>> 0 02:32 pts/8 00:00:00 grep --color=auto 6703
>>>
>>> and this command  netstat -netulp | grep 2181 and got this
>>>  (Not all processes could be identified, non-owned process info will
>>> not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
>>> :::* LISTEN 1000 14805 2301/java
>>>
>>
>>
>
>
> --
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh
>


>>>
>>>
>>> --
>>> Nick R. Katsipoulakis,
>>> Department of Computer Science
>>> University of Pittsburgh
>>>
>>
>>
>
>
> --
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh
>

Re: Error on initialization

2015-11-07 Thread researcher cs

i don't mean anything but why you said that ?  just i'm asking to got what
you wrote i'm confused only , Sorry for everyone  here Thanks for help sure



On Sat, Nov 7, 2015 at 5:21 PM, Fan Jiang  wrote:

> Type in "sudo netstat -antlp|grep 6703" to see if it returns anything - it
> should in your case. The rightmost column in the result is the PID of the
> running process using the port. The you can type in "sudo ps -ef|grep
> " to see what the exact process is. Make sure you prefix the commands
> with "sudo" so that you can search among all processes running on the
> machine.
>
> Please be nice to others who answer your question nicely. Nobody owe you
> an answer.
>
> —
> Sincerely,
> Fan Jiang
>
>
> On Sat, Nov 7, 2015 at 8:07 PM, Nick R. Katsipoulakis <
> nick.kat...@gmail.com> wrote:
>
>> Then I guess it means that another process is using port 6703. That means
>> that the supervisor (Storm) can not start worker process on port 6703 and
>> that is why you get the previous error.
>>
>> I hope the above helps.
>>
>> Nick
>>
>> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs 
>> wrote:
>>
>>> sorry this command ps -ef|grep 6703 got this result username 3299 2766
>>> 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>>>
>>> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs >> > wrote:
>>>
 i used this command ps -ef|grep 6703 and got this username 4162 3449 0
 02:32 pts/8 00:00:00 grep --color=auto 6703

 and this command  netstat -netulp | grep 2181 and got this
  (Not all processes could be identified, non-owned process info will
 not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
 :::* LISTEN 1000 14805 2301/java

>>>
>>>
>>
>>
>> --
>> Nick R. Katsipoulakis,
>> Department of Computer Science
>> University of Pittsburgh
>>
>
>

Re: Error on initialization

2015-11-07 Thread researcher cs

i hope you can get what i mean ?!

On Sat, Nov 7, 2015 at 5:21 PM, Nick R. Katsipoulakis  wrote:

> Hello again,
>
> Because the error you posted has the following:
>
> *[ERROR] Error on initialization of server mk-worker
> org.apache.storm.netty.channel.ChannelException: Failed to bind
> to: 0.0.0.0/0.0.0.0:6703 *
>
> If that is not the ERROR then you should post the proper part of your log.
>
> Nick
>
> On Sat, Nov 7, 2015 at 8:17 PM, researcher cs 
> wrote:
>
>> i'm just asking why you guess that there are another process using port
>> 6703 ?!!!
>> and my supervisor using one worker only
>>
>> On Sat, Nov 7, 2015 at 5:13 PM, Nick R. Katsipoulakis <
>> nick.kat...@gmail.com> wrote:
>>
>>> Well, if that is the case then that means that another worker process is
>>> already active. You have to go through the supervisor.log to see if Storm
>>> has another worker process running.
>>>
>>> Nick
>>>
>>> On Sat, Nov 7, 2015 at 8:09 PM, researcher cs >> > wrote:
>>>
 sorry how do you know if that any other process using port 6703 ?! i'm
 now running storm and think that this process for it ! am i right or wrong 
 ?

 3299 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703

 On Sat, Nov 7, 2015 at 5:06 PM, Nick R. Katsipoulakis <
 nick.kat...@gmail.com> wrote:

> Then I guess it means that another process is using port 6703. That
> means that the supervisor (Storm) can not start worker process on port 
> 6703
> and that is why you get the previous error.
>
> I hope the above helps.
>
> Nick
>
> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs <
> prog.researc...@gmail.com> wrote:
>
>> sorry this command ps -ef|grep 6703 got this result username 3299
>> 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>>
>> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs <
>> prog.researc...@gmail.com> wrote:
>>
>>> i used this command ps -ef|grep 6703 and got this username 4162 3449
>>> 0 02:32 pts/8 00:00:00 grep --color=auto 6703
>>>
>>> and this command  netstat -netulp | grep 2181 and got this
>>>  (Not all processes could be identified, non-owned process info will
>>> not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
>>> :::* LISTEN 1000 14805 2301/java
>>>
>>
>>
>
>
> --
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh
>


>>>
>>>
>>> --
>>> Nick R. Katsipoulakis,
>>> Department of Computer Science
>>> University of Pittsburgh
>>>
>>
>>
>
>
> --
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh
>

Re: Error on initialization

2015-11-07 Thread researcher cs

Thanks for your patience , i restarted the topology
then same error still then executed your command here what i got
username 4453 46.0 8.5 1010020 94564 pts/3 Sl+ 03:49 2:38
/usr/lib/jvm/jdk1.6.0_38/bin/java -server -Xmx768m
-Djava.library.path=/home/st/storm/datadir/storm/supervisor/stormdist/topology
-1446947394/resources/Linux-i386:/home/st/storm/datadir/storm/supervisor/stormdist/topology-1-1446947394/resources:/usr/local/lib:/opt/local/lib:/usr/lib
-Dlogfile.name=worker-6703.log
-Dstorm.home=/home/username/storm/apache-storm-0.9.5 -Dstorm.conf.file=
-Dstorm.options=
-Dstorm.log.dir=/home/username/storm/apache-storm-0.9.5/logs
-Dlogback.configurationFile=/home/username/storm/apache-storm-0.9.5/logback/cluster.xml
-Dstorm.id=fsd-1-1446947394
-Dworker.id=d1a24944-25ac-447a-8e6d-b78805cedef7 -Dworker.port=6703 -cp
/home/username/storm/apache-storm-0.9.5/lib/jline-2.11.jar:/home/username/storm/apache-storm-0.9.5/lib/objenesis-1.2.jar:/home/username/storm/apache-storm-0.9.5/lib/carbonite-1.4.0.jar:/home/usernamet/storm/apache-storm-0.9.5/lib/disruptor-2.10.1.jar:/home/username/storm/apache-storm-0.9.5/lib/ring-core-1.1.5.jar:/home/username/storm/apache-storm-0.9.5/lib/tools.logging-0.2.3.jar:/home/username/storm/apache-storm-0.9.5/lib/hiccup-0.3.6.jar:/home/username/storm/apache-storm-0.9.5/lib/servlet-api-2.5.jar:/home/username/storm/apache-storm-0.9.5/lib/clj-stacktrace-0.2.2.jar:/home/username/storm/apache-storm-0.9.5/lib/reflectasm-1.07-shaded.jar:/home/username/storm/apache-storm-0.9.5/lib/commons-logging-1.1.3.jar:/home/username/storm/apache-storm-0.9.5/lib/tools.cli-0.2.4.jar:/home/username/storm/apache-storm-0.9.5/lib/clojure-1.5.1.jar:/home/username/storm/apache-storm-0.9.5/lib/logback-core-1.0.13.jar:/home/username/storm/apache-storm-0.9.5/lib/clout-1.0.1.jar:/home/username/storm/apache-storm-0.9.5/lib/core.incubator-0.1.0.jar:/home/username/storm/apache-storm-0.9.5/lib/ring-jetty-adapter-0.3.11.jar:/home/username/storm/apache-storm-0.9.5/lib/asm-4.0.jar:/home/username/storm/apache-storm-0.9.5/lib/jgrapht-core-0.9.0.jar:/home/username/storm/apache-storm-0.9.5/lib/slf4j-api-1.7.5.jar:/home/username/storm/apache-storm-0.9.5/lib/storm-core-0.9.5.jar:/home/username/storm/apache-storm-0.9.5/lib/commons-fileupload-1.2.1.jar:/home/username/storm/apache-storm-0.9.5/lib/commons-exec-1.1.jar:/home/username/storm/apache-storm-0.9.5/lib/minlog-1.2.jar:/home/username/storm/apache-storm-0.9.5/lib/ring-servlet-0.3.11.jar:/home/st/storm/apache-storm-0.9.5/lib/clj-time-0.4.1.jar:/home/username/storm/apache-storm-0.9.5/lib/jetty-util-6.1.26.jar:/home/username/storm/apache-storm-0.9.5/lib/tools.macro-0.1.0.jar:/home/username/storm/apache-storm-0.9.5/lib/jetty-6.1.26.jar:/home/st/storm/apache-storm-0.9.5/lib/json-simple-1.1.jar:/home/st/storm/apache-storm-0.9.5/lib/log4j-over-slf4j-1.6.6.jar:/home/username/storm/apache-storm-0.9.5/lib/kryo-2.21.jar:/home/st/storm/apache-storm-0.9.5/lib/commons-codec-1.6.jar:/home/st/storm/apache-storm-0.9.5/lib/chill-java-0.3.5.jar:/home/st/storm/apache-storm-0.9.5/lib/snakeyaml-1.11.jar:/home/st/storm/apache-storm-0.9.5/lib/logback-classic-1.0.13.jar:/home/st/storm/apache-storm-0.9.5/lib/math.numeric-tower-0.0.1.jar:/home/st/storm/apache-storm-0.9.5/lib/commons-io-2.4.jar:/home/st/storm/apache-storm-0.9.5/lib/compojure-1.1.3.jar:/home/st/storm/apache-storm-0.9.5/lib/commons-lang-2.5.jar:/home/st/storm/apache-storm-0.9.5/lib/ring-devel-0.3.11.jar:/home/st/storm/apache-storm-0.9.5/lib/joda-time-2.0.jar:/home/st/storm/apache-storm-0.9.5/conf:/home/st/storm/datadir/storm/supervisor/stormdist/topology-1-1446947394/stormjar.jar
backtype.storm.daemon.worker topology-1-1446947394
a822c5d7-e399-4ed3-8303-81ba904b961b 6703
d1a24944-25ac-447a-8e6d-b78805cedef7 st 4722 0.0 0.0 4388 816 pts/7 R+
03:55 0:00 grep --color=auto 4453



On Sat, Nov 7, 2015 at 5:50 PM, Fan Jiang  wrote:

> Then do a "sudo ps aux|grep 2963" to see if anything is returned.
>
> —
> Sincerely,
> Fan Jiang
>
>
> On Sat, Nov 7, 2015 at 8:45 PM, researcher cs 
> wrote:
>
>> i tried to run
>> username@ubuntu:~$ sudo netstat -antlp|grep 2181
>> tcp6 0 0 :::2181 :::* LISTEN 2301/java
>> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65107 ESTABLISHED 2301/java
>> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65105 ESTABLISHED 2301/java
>> tcp6 0 0 127.0.0.1:65110 127.0.0.1:2181 ESTABLISHED 2512/java
>> tcp6 0 0 127.0.0.1:65122 127.0.0.1:2181 ESTABLISHED 2963/java
>> tcp6 0 0 127.0.0.1:65107 127.0.0.1:2181 ESTABLISHED 2415/java
>> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65110 ESTABLISHED 2301/java
>> tcp6 0 0 127.0.0.1:65105 127.0.0.1:2181 ESTABLISHED 2319/java
>> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65122 ESTABLISHED 2301/java
>>
>>
>>
>> On Sat, Nov 7, 2015 at 5:40 PM, researcher cs 
>> wrote:
>>
>>> ok i tried to run this "sudo netstat -antlp|grep 6703" and got this
>>> tcp6 0 0 :::6703 :::* LISTEN 2963/java
>>>
>>> here did you mean the pid is 2963 if that i got nothing when ran
>>>

Re: Error on initialization

2015-11-07 Thread Nick R. Katsipoulakis

Hello,

It seems that port 6703 can not be binded for the worker. Are you sure that
this port is not used by another process?

Nick

On Sat, Nov 7, 2015 at 7:10 PM, researcher cs 
wrote:

> this happened when submitted topology
>
> On Sat, Nov 7, 2015 at 4:09 PM, researcher cs 
> wrote:
>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *here what i got in worker log file [ERROR] Error on initialization of
>> server mk-worker org.apache.storm.netty.channel.ChannelException: Failed to
>> bind to: 0.0.0.0/0.0.0.0:6703  at
>> org.apache.storm.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> backtype.storm.messaging.netty.Server.(Server.java:130)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> backtype.storm.messaging.netty.Context.bind(Context.java:75)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> backtype.storm.messaging.loader$launch_receive_thread_BANG_.doInvoke(loader.clj:68)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> clojure.lang.RestFn.invoke(RestFn.java:668) [clojure-1.5.1.jar:na] at
>> backtype.storm.daemon.worker$launch_receive_thread.invoke(worker.clj:378)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> backtype.storm.daemon.worker$fn__6959$exec_fn__1103__auto6960.invoke(worker.clj:413)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> clojure.lang.AFn.applyToHelper(AFn.java:185) [clojure-1.5.1.jar:na] at
>> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
>> clojure.core$apply.invoke(core.clj:617) ~[clojure-1.5.1.jar:na] at
>> backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
>> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
>> [clojure-1.5.1.jar:na] at
>> backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
>> [storm-core-0.9.5.jar:0.9.5] at
>> clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
>> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
>> backtype.storm.daemon.worker.main(Unknown Source)
>> [storm-core-0.9.5.jar:0.9.5] java.net.BindException: Address already in use
>> at sun.nio.ch.Net.bind(Native Method) ~[na:1.6.0_38] at
>> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124)
>> ~[na:1.6.0_38] at
>> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>> ~[na:1.6.0_38] at
>> org.apache.storm.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> org.apache.storm.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> org.apache.storm.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> org.apache.storm.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> org.apache.storm.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
>> ~[storm-core-0.9.5.jar:0.9.5] at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> ~[na:1.6.0_38] at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> ~[na:1.6.0_38] at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_38]and
>> this when executed the command that launch supervisor and worker  cause of
>> supervisor still hasn't start *
>>
>>
>>
>> *[ERROR] Halting process: ("Error on initialization")
>> java.lang.RuntimeException: ("Error on initialization") at
>> backtype.storm.util$exit_process_BANG_.doInvoke(util.clj:325)
>> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:423)
>> [clojure-1.5.1.jar:na] at
>> backtype.storm.daemon.worker$fn__6959$mk_worker__7015.doInvoke(worker.clj:391)
>> [storm-core-0.9.5.jar:0.9.5] at clojure.lang.RestFn.invoke(RestFn.java:512)
>> [clojure-1.5.1.jar:na] at
>> backtype.storm.daemon.worker$_main.invoke(worker.clj:502)
>> [storm-core-0.9.5.jar:0.9.5] at
>> clojure.lang.AFn.applyToHelper(AFn.java:172) [clojure-1.5.1.jar:na] at
>> clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.5.1.jar:na] at
>> backtype.storm.daemon.worker.main(Unknown Source)
>> [storm-core-0.9.5.jar:0.9.5]*
>>
>> *storm version 0.9.5 *
>>
>> *zookeeper -3.4.6 *
>>
>
>


-- 
Nick R. Katsipoulakis,
Department of Computer Science
University of Pittsburgh

Re: Error on initialization

2015-11-07 Thread Nick R. Katsipoulakis

Then I guess it means that another process is using port 6703. That means
that the supervisor (Storm) can not start worker process on port 6703 and
that is why you get the previous error.

I hope the above helps.

Nick

On Sat, Nov 7, 2015 at 7:58 PM, researcher cs 
wrote:

> sorry this command ps -ef|grep 6703 got this result username 3299 2766 0
> 02:55 pts/7 00:00:00 grep --color=auto 6703
>
> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs 
> wrote:
>
>> i used this command ps -ef|grep 6703 and got this username 4162 3449 0
>> 02:32 pts/8 00:00:00 grep --color=auto 6703
>>
>> and this command  netstat -netulp | grep 2181 and got this
>>  (Not all processes could be identified, non-owned process info will not
>> be shown, you would have to be root to see it all.) tcp6 0 0 :::2181 :::*
>> LISTEN 1000 14805 2301/java
>>
>
>


-- 
Nick R. Katsipoulakis,
Department of Computer Science
University of Pittsburgh

Re: Error on initialization

2015-11-07 Thread researcher cs

sorry how do you know if that any other process using port 6703 ?! i'm now
running storm and think that this process for it ! am i right or wrong ?

3299 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703

On Sat, Nov 7, 2015 at 5:06 PM, Nick R. Katsipoulakis  wrote:

> Then I guess it means that another process is using port 6703. That means
> that the supervisor (Storm) can not start worker process on port 6703 and
> that is why you get the previous error.
>
> I hope the above helps.
>
> Nick
>
> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs 
> wrote:
>
>> sorry this command ps -ef|grep 6703 got this result username 3299 2766 0
>> 02:55 pts/7 00:00:00 grep --color=auto 6703
>>
>> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs 
>> wrote:
>>
>>> i used this command ps -ef|grep 6703 and got this username 4162 3449 0
>>> 02:32 pts/8 00:00:00 grep --color=auto 6703
>>>
>>> and this command  netstat -netulp | grep 2181 and got this
>>>  (Not all processes could be identified, non-owned process info will not
>>> be shown, you would have to be root to see it all.) tcp6 0 0 :::2181 :::*
>>> LISTEN 1000 14805 2301/java
>>>
>>
>>
>
>
> --
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh
>

Re: Error on initialization

2015-11-07 Thread Nick R. Katsipoulakis

Hello again,

Because the error you posted has the following:

*[ERROR] Error on initialization of server mk-worker
org.apache.storm.netty.channel.ChannelException: Failed to bind
to: 0.0.0.0/0.0.0.0:6703 *

If that is not the ERROR then you should post the proper part of your log.

Nick

On Sat, Nov 7, 2015 at 8:17 PM, researcher cs 
wrote:

> i'm just asking why you guess that there are another process using port
> 6703 ?!!!
> and my supervisor using one worker only
>
> On Sat, Nov 7, 2015 at 5:13 PM, Nick R. Katsipoulakis <
> nick.kat...@gmail.com> wrote:
>
>> Well, if that is the case then that means that another worker process is
>> already active. You have to go through the supervisor.log to see if Storm
>> has another worker process running.
>>
>> Nick
>>
>> On Sat, Nov 7, 2015 at 8:09 PM, researcher cs 
>> wrote:
>>
>>> sorry how do you know if that any other process using port 6703 ?! i'm
>>> now running storm and think that this process for it ! am i right or wrong ?
>>>
>>> 3299 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>>>
>>> On Sat, Nov 7, 2015 at 5:06 PM, Nick R. Katsipoulakis <
>>> nick.kat...@gmail.com> wrote:
>>>
 Then I guess it means that another process is using port 6703. That
 means that the supervisor (Storm) can not start worker process on port 6703
 and that is why you get the previous error.

 I hope the above helps.

 Nick

 On Sat, Nov 7, 2015 at 7:58 PM, researcher cs <
 prog.researc...@gmail.com> wrote:

> sorry this command ps -ef|grep 6703 got this result username 3299
> 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>
> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs <
> prog.researc...@gmail.com> wrote:
>
>> i used this command ps -ef|grep 6703 and got this username 4162 3449
>> 0 02:32 pts/8 00:00:00 grep --color=auto 6703
>>
>> and this command  netstat -netulp | grep 2181 and got this
>>  (Not all processes could be identified, non-owned process info will
>> not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
>> :::* LISTEN 1000 14805 2301/java
>>
>
>


 --
 Nick R. Katsipoulakis,
 Department of Computer Science
 University of Pittsburgh

>>>
>>>
>>
>>
>> --
>> Nick R. Katsipoulakis,
>> Department of Computer Science
>> University of Pittsburgh
>>
>
>


-- 
Nick R. Katsipoulakis,
Department of Computer Science
University of Pittsburgh

Re: Error on initialization

2015-11-07 Thread researcher cs

i'm just asking why you guess that there are another process using port
6703 ?!!!
and my supervisor using one worker only

On Sat, Nov 7, 2015 at 5:13 PM, Nick R. Katsipoulakis  wrote:

> Well, if that is the case then that means that another worker process is
> already active. You have to go through the supervisor.log to see if Storm
> has another worker process running.
>
> Nick
>
> On Sat, Nov 7, 2015 at 8:09 PM, researcher cs 
> wrote:
>
>> sorry how do you know if that any other process using port 6703 ?! i'm
>> now running storm and think that this process for it ! am i right or wrong ?
>>
>> 3299 2766 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>>
>> On Sat, Nov 7, 2015 at 5:06 PM, Nick R. Katsipoulakis <
>> nick.kat...@gmail.com> wrote:
>>
>>> Then I guess it means that another process is using port 6703. That
>>> means that the supervisor (Storm) can not start worker process on port 6703
>>> and that is why you get the previous error.
>>>
>>> I hope the above helps.
>>>
>>> Nick
>>>
>>> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs >> > wrote:
>>>
 sorry this command ps -ef|grep 6703 got this result username 3299 2766
 0 02:55 pts/7 00:00:00 grep --color=auto 6703

 On Sat, Nov 7, 2015 at 4:57 PM, researcher cs <
 prog.researc...@gmail.com> wrote:

> i used this command ps -ef|grep 6703 and got this username 4162 3449 0
> 02:32 pts/8 00:00:00 grep --color=auto 6703
>
> and this command  netstat -netulp | grep 2181 and got this
>  (Not all processes could be identified, non-owned process info will
> not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
> :::* LISTEN 1000 14805 2301/java
>


>>>
>>>
>>> --
>>> Nick R. Katsipoulakis,
>>> Department of Computer Science
>>> University of Pittsburgh
>>>
>>
>>
>
>
> --
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh
>

Re: Error on initialization

2015-11-07 Thread Fan Jiang

Type in "sudo netstat -antlp|grep 6703" to see if it returns anything - it 
should in your case. The rightmost column in the result is the PID of the 
running process using the port. The you can type in "sudo ps -ef|grep " to 
see what the exact process is. Make sure you prefix the commands with "sudo" so 
that you can search among all processes running on the machine. 

Please be nice to others who answer your question nicely. Nobody owe you an 
answer. 

—
Sincerely,
Fan Jiang

On Sat, Nov 7, 2015 at 8:07 PM, Nick R. Katsipoulakis
 wrote:

> Then I guess it means that another process is using port 6703. That means
> that the supervisor (Storm) can not start worker process on port 6703 and
> that is why you get the previous error.
> I hope the above helps.
> Nick
> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs 
> wrote:
>> sorry this command ps -ef|grep 6703 got this result username 3299 2766 0
>> 02:55 pts/7 00:00:00 grep --color=auto 6703
>>
>> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs 
>> wrote:
>>
>>> i used this command ps -ef|grep 6703 and got this username 4162 3449 0
>>> 02:32 pts/8 00:00:00 grep --color=auto 6703
>>>
>>> and this command  netstat -netulp | grep 2181 and got this
>>>  (Not all processes could be identified, non-owned process info will not
>>> be shown, you would have to be root to see it all.) tcp6 0 0 :::2181 :::*
>>> LISTEN 1000 14805 2301/java
>>>
>>
>>
> -- 
> Nick R. Katsipoulakis,
> Department of Computer Science
> University of Pittsburgh

Re: Error on initialization

2015-11-07 Thread researcher cs

ok i tried to run this "sudo netstat -antlp|grep 6703" and got this
tcp6 0 0 :::6703 :::* LISTEN 2963/java

here did you mean the pid is 2963 if that i got nothing when ran
sudo ps -ef|grep 2963




On Sat, Nov 7, 2015 at 5:21 PM, Fan Jiang  wrote:

> Type in "sudo netstat -antlp|grep 6703" to see if it returns anything - it
> should in your case. The rightmost column in the result is the PID of the
> running process using the port. The you can type in "sudo ps -ef|grep
> " to see what the exact process is. Make sure you prefix the commands
> with "sudo" so that you can search among all processes running on the
> machine.
>
> Please be nice to others who answer your question nicely. Nobody owe you
> an answer.
>
> —
> Sincerely,
> Fan Jiang
>
>
> On Sat, Nov 7, 2015 at 8:07 PM, Nick R. Katsipoulakis <
> nick.kat...@gmail.com> wrote:
>
>> Then I guess it means that another process is using port 6703. That means
>> that the supervisor (Storm) can not start worker process on port 6703 and
>> that is why you get the previous error.
>>
>> I hope the above helps.
>>
>> Nick
>>
>> On Sat, Nov 7, 2015 at 7:58 PM, researcher cs 
>> wrote:
>>
>>> sorry this command ps -ef|grep 6703 got this result username 3299 2766
>>> 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>>>
>>> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs >> > wrote:
>>>
 i used this command ps -ef|grep 6703 and got this username 4162 3449 0
 02:32 pts/8 00:00:00 grep --color=auto 6703

 and this command  netstat -netulp | grep 2181 and got this
  (Not all processes could be identified, non-owned process info will
 not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
 :::* LISTEN 1000 14805 2301/java

>>>
>>>
>>
>>
>> --
>> Nick R. Katsipoulakis,
>> Department of Computer Science
>> University of Pittsburgh
>>
>
>

Re: Error on initialization

2015-11-07 Thread Fan Jiang

Then do a "sudo ps aux|grep 2963" to see if anything is returned.



—
Sincerely,
Fan Jiang

On Sat, Nov 7, 2015 at 8:45 PM, researcher cs 
wrote:

> i tried to run
> username@ubuntu:~$ sudo netstat -antlp|grep 2181
> tcp6 0 0 :::2181 :::* LISTEN 2301/java
> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65107 ESTABLISHED 2301/java
> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65105 ESTABLISHED 2301/java
> tcp6 0 0 127.0.0.1:65110 127.0.0.1:2181 ESTABLISHED 2512/java
> tcp6 0 0 127.0.0.1:65122 127.0.0.1:2181 ESTABLISHED 2963/java
> tcp6 0 0 127.0.0.1:65107 127.0.0.1:2181 ESTABLISHED 2415/java
> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65110 ESTABLISHED 2301/java
> tcp6 0 0 127.0.0.1:65105 127.0.0.1:2181 ESTABLISHED 2319/java
> tcp6 0 0 127.0.0.1:2181 127.0.0.1:65122 ESTABLISHED 2301/java
> On Sat, Nov 7, 2015 at 5:40 PM, researcher cs 
> wrote:
>> ok i tried to run this "sudo netstat -antlp|grep 6703" and got this
>> tcp6 0 0 :::6703 :::* LISTEN 2963/java
>>
>> here did you mean the pid is 2963 if that i got nothing when ran
>> sudo ps -ef|grep 2963
>>
>>
>>
>>
>> On Sat, Nov 7, 2015 at 5:21 PM, Fan Jiang  wrote:
>>
>>> Type in "sudo netstat -antlp|grep 6703" to see if it returns anything -
>>> it should in your case. The rightmost column in the result is the PID of
>>> the running process using the port. The you can type in "sudo ps -ef|grep
>>> " to see what the exact process is. Make sure you prefix the commands
>>> with "sudo" so that you can search among all processes running on the
>>> machine.
>>>
>>> Please be nice to others who answer your question nicely. Nobody owe you
>>> an answer.
>>>
>>> —
>>> Sincerely,
>>> Fan Jiang
>>>
>>>
>>> On Sat, Nov 7, 2015 at 8:07 PM, Nick R. Katsipoulakis <
>>> nick.kat...@gmail.com> wrote:
>>>
 Then I guess it means that another process is using port 6703. That
 means that the supervisor (Storm) can not start worker process on port 6703
 and that is why you get the previous error.

 I hope the above helps.

 Nick

 On Sat, Nov 7, 2015 at 7:58 PM, researcher cs  wrote:

> sorry this command ps -ef|grep 6703 got this result username 3299 2766
> 0 02:55 pts/7 00:00:00 grep --color=auto 6703
>
> On Sat, Nov 7, 2015 at 4:57 PM, researcher cs <
> prog.researc...@gmail.com> wrote:
>
>> i used this command ps -ef|grep 6703 and got this username 4162 3449 0
>> 02:32 pts/8 00:00:00 grep --color=auto 6703
>>
>> and this command  netstat -netulp | grep 2181 and got this
>>  (Not all processes could be identified, non-owned process info will
>> not be shown, you would have to be root to see it all.) tcp6 0 0 :::2181
>> :::* LISTEN 1000 14805 2301/java
>>
>
>


 --
 Nick R. Katsipoulakis,
 Department of Computer Science
 University of Pittsburgh

>>>
>>>
>>

Question about acker behavior and tuple timeouts

2015-11-07 Thread Stephen Powis

So this question may be better suited for the dev mailing list, but
I'll give this a shot.

I'm trying to better understand the acker behavior and how it deals
with tuple time outs.  I've read the documentation on the storm
website, but from my rudimentary knowledge of clojure, it seems like
the docs and the code don't completely align.

The short of it is I'm wondering if the line linked in acker.clj
resets the tuple timeout value every time a bolt acks a tuple:
https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/daemon/acker.clj#L65

It seems like for every tuple coming into the acker, it calls
rotatingMap.put() on the instance, which in turn resets its timeout
countdown.

Does this sound correct?

Re: KafkaSpout starts from 0 after restart

Store previous calculated result

Re: Error on initialization

Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Need help in this problem " Address already in use(0x62)"

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Re: Error on initialization

Question about acker behavior and tuple timeouts

24 matches

Site Navigation

Mail list logo

Footer information