Re: Pluggable Scheduling Worker Problem

Thu, 06 Nov 2014 02:03:08 -0800 

Don't mention it :)

Can't you see any traces from Storm's EvenScheduler in nimbus.log?

Ahmed

On 11/06/2014 10:47 AM, swapnil joshi wrote:

Hi Ahmed,
First I am saying thank you for your immediate response
Log information as follow :
Scheduler Log :
DemoScheduler: begin scheduling
FInalise scheduling
DemoScheduler: begin scheduling
FInalise scheduling
DemoScheduler: begin scheduling
FInalise scheduling
DemoScheduler: begin scheduling
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]], special-spout=[[2, 2]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [2, 2]=special-spout, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {}
Our special-spout needs scheduling.
 SuperVisorrrrrrrrrrrrrrrrrrrrr
Meta Name ======= normal-supervisor
 SuperVisorrrrrrrrrrrrrrrrrrrrr
Meta Name ======= special-supervisor
Found the special-supervisor
WWWWWWWWWWWWe assigned executors:[[2, 2]] to slot: [6378cebb-463e-407d-b4fe-45a8a18bbf38, 6710] 
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
Our special topology needs scheduling.
needs scheduling(component->executor): {__acker=[[1, 1]], word-counter=[[3, 3]], word-normalizer=[[4, 4]]} needs scheduling(executor->compoenents): {[3, 3]=word-counter, [1, 1]=__acker, [4, 4]=word-normalizer} 
current assignments: {[2, 2]=6378cebb-463e-407d-b4fe-45a8a18bbf38:6710}
Our special-spout DOES NOT NEED scheduling.
FInalise scheduling
DemoScheduler: begin scheduling
FInalise scheduling

Supervisor Log:
2014-11-06 14:25:10 b.s.d.supervisor [INFO] d0f56b71-5229-4974-8120-41f368f7f29a still hasn't started 2014-11-06 14:25:11 b.s.d.supervisor [INFO] d0f56b71-5229-4974-8120-41f368f7f29a still hasn't started 2014-11-06 14:25:11 b.s.d.supervisor [INFO] d0f56b71-5229-4974-8120-41f368f7f29a still hasn't started 2014-11-06 14:25:12 b.s.d.supervisor [INFO] d0f56b71-5229-4974-8120-41f368f7f29a still hasn't started 2014-11-06 14:25:12 b.s.d.supervisor [INFO] d0f56b71-5229-4974-8120-41f368f7f29a still hasn't started 2014-11-06 14:25:13 b.s.d.supervisor [INFO] d0f56b71-5229-4974-8120-41f368f7f29a still hasn't started 2014-11-06 14:25:13 b.s.d.supervisor [INFO] d0f56b71-5229-4974-8120-41f368f7f29a still hasn't started 

Nimbus Log As I provided in above mail

Zookeeper Log
68.1.13:49582
2014-11-06 14:25:13,720 [myid:] - INFO [SyncThread:0:ZooKeeperServer@617] - Established session 0x149844d9f4e0007 with negotiated timeout 20000 for client /192.168.1.13:49582 <http://192.168.1.13:49582> 2014-11-06 14:28:46,614 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357>] - caught end of stream exception EndOfStreamException: Unable to read additional data from client sessionid 0x149844d9f4e0007, likely client has closed socket at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228) at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208) 
        at java.lang.Thread.run(Thread.java:745)
2014-11-06 14:28:46,618 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007>] - Closed socket connection for client /192.168.1.13:49582 <http://192.168.1.13:49582> which had sessionid 0x149844d9f4e0007 2014-11-06 14:29:06,000 [myid:] - INFO [SessionTracker:ZooKeeperServer@347] - Expiring session 0x149844d9f4e0007, timeout of 20000ms exceeded 2014-11-06 14:29:06,001 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x149844d9f4e0007 2014-11-06 14:47:13,300 [myid:] - WARN [SyncThread:0:FileTxnLog@334] - fsync-ing the write ahead log in SyncThread:0 took 1088ms which will adversely effect operation latency. See the ZooKeeper troubleshooting guide 2014-11-06 14:53:45,547 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357>] - caught end of stream exception EndOfStreamException: Unable to read additional data from client sessionid 0x149844d9f4e0005, likely client has closed socket at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228) at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208) 
        at java.lang.Thread.run(Thread.java:745)
2014-11-06 14:53:45,548 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007>] - Closed socket connection for client /192.168.1.2:41944 <http://192.168.1.2:41944> which had sessionid 0x149844d9f4e0005 2014-11-06 14:53:52,394 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357>] - caught end of stream exception EndOfStreamException: Unable to read additional data from client sessionid 0x149844d9f4e0003, likely client has closed socket at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228) at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208) 
        at java.lang.Thread.run(Thread.java:745)
2014-11-06 14:53:52,395 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007>] - Closed socket connection for client /192.168.1.13:49571 <http://192.168.1.13:49571> which had sessionid 0x149844d9f4e0003 2014-11-06 14:54:04,000 [myid:] - INFO [SessionTracker:ZooKeeperServer@347] - Expiring session 0x149844d9f4e0005, timeout of 20000ms exceeded 2014-11-06 14:54:04,001 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x149844d9f4e0005 2014-11-06 14:54:05,839 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x149844d9f4e0001 2014-11-06 14:54:05,856 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007>] - Closed socket connection for client /192.168.1.13:49569 <http://192.168.1.13:49569> which had sessionid 0x149844d9f4e0001 2014-11-06 14:54:12,000 [myid:] - INFO [SessionTracker:ZooKeeperServer@347] - Expiring session 0x149844d9f4e0003, timeout of 20000ms exceeded 2014-11-06 14:54:12,000 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x149844d9f4e0003 2014-11-06 14:59:48,769 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197>] - Accepted socket connection from /192.168.1.13:50491 <http://192.168.1.13:50491> 2014-11-06 14:59:48,771 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822>] - Connection request from old client /192.168.1.13:50491 <http://192.168.1.13:50491>; will be dropped if server is in r-o mode 2014-11-06 14:59:48,771 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868>] - Client attempting to establish new session at /192.168.1.13:50491 <http://192.168.1.13:50491> 2014-11-06 14:59:48,789 [myid:] - INFO [SyncThread:0:ZooKeeperServer@617] - Established session 0x149844d9f4e0008 with negotiated timeout 20000 for client /192.168.1.13:50491 <http://192.168.1.13:50491> 2014-11-06 14:59:48,796 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x149844d9f4e0008 2014-11-06 14:59:48,800 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007>] - Closed socket connection for client /192.168.1.13:50491 <http://192.168.1.13:50491> which had sessionid 0x149844d9f4e0008 2014-11-06 14:59:48,802 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197>] - Accepted socket connection from /192.168.1.13:50492 <http://192.168.1.13:50492> 2014-11-06 14:59:48,802 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822>] - Connection request from old client /192.168.1.13:50492 <http://192.168.1.13:50492>; will be dropped if server is in r-o mode 2014-11-06 14:59:48,802 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868>] - Client attempting to establish new session at /192.168.1.13:50492 <http://192.168.1.13:50492> 2014-11-06 14:59:48,811 [myid:] - INFO [SyncThread:0:ZooKeeperServer@617] - Established session 0x149844d9f4e0009 with negotiated timeout 20000 for client /192.168.1.13:50492 <http://192.168.1.13:50492> 2014-11-06 15:00:01,131 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197>] - Accepted socket connection from /192.168.1.13:50493 <http://192.168.1.13:50493> 2014-11-06 15:00:01,135 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822>] - Connection request from old client /192.168.1.13:50493 <http://192.168.1.13:50493>; will be dropped if server is in r-o mode 2014-11-06 15:00:01,135 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868>] - Client attempting to establish new session at /192.168.1.13:50493 <http://192.168.1.13:50493> 2014-11-06 15:00:01,158 [myid:] - INFO [SyncThread:0:ZooKeeperServer@617] - Established session 0x149844d9f4e000a with negotiated timeout 20000 for client /192.168.1.13:50493 <http://192.168.1.13:50493> 2014-11-06 15:00:01,172 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x149844d9f4e000a 2014-11-06 15:00:01,180 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007>] - Closed socket connection for client /192.168.1.13:50493 <http://192.168.1.13:50493> which had sessionid 0x149844d9f4e000a 2014-11-06 15:00:01,195 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197>] - Accepted socket connection from /192.168.1.13:50494 <http://192.168.1.13:50494> 2014-11-06 15:00:01,196 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@822>] - Connection request from old client /192.168.1.13:50494 <http://192.168.1.13:50494>; will be dropped if server is in r-o mode 2014-11-06 15:00:01,196 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868 <http://0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868>] - Client attempting to establish new session at /192.168.1.13:50494 <http://192.168.1.13:50494> 2014-11-06 15:00:01,202 [myid:] - INFO [SyncThread:0:ZooKeeperServer@617] - Established session 0x149844d9f4e000b with negotiated timeout 20000 for client /192.168.1.13:50494 <http://192.168.1.13:50494> 2014-11-06 15:11:36,380 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x149844d9f4e0009 2014-11-06 15:11:36,403 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007 <http://0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1007>] - Closed socket connection for client /192.168.1.13:50492 <http://192.168.1.13:50492> which had sessionid 0x149844d9f4e0009
On Thu, Nov 6, 2014 at 2:58 PM, Ahmed El Rheddane <[email protected] <mailto:[email protected]>> wrote: 

    Can you share the Scheduler's logs as well?

    Ahmed


    On 11/06/2014 09:56 AM, swapnil joshi wrote:

    yes, I had checked. "new EvenScheduler().schedule(topol
    ogies, cluster);" called at end.

    On Thu, Nov 6, 2014 at 2:12 PM, Ahmed El Rheddane
    <[email protected] <mailto:[email protected]>> wrote:

        Hi,

        Are you sure you called "new
        EvenScheduler().schedule(topologies, cluster);" at the end of
        the schedule method?

        Ahmed


        On 11/06/2014 08:01 AM, swapnil joshi wrote:

            Hi Storm,

            I am new with storm. I want schedule my topology. I got
            some use full inofrmation on following address :
            
http://xumingming.sinaapp.com/885/twitter-storm-how-to-develop-a-pluggable-scheduler/

            But when i am submitting my topology to my storm cluster.
            special spout is running on special supervisor machine
            but it does not start may other bolt.

            At nimbus log, I got following error :
            2014-11-05 19:24:55 b.s.d.nimbus [INFO] Executor
            special-topology-1-1415195688:[3 3] not alive
            2014-11-05 19:24:55 b.s.d.nimbus [INFO] Executor
            special-topology-1-1415195688:[4 4] not alive
            2014-11-05 19:24:55 b.s.d.nimbus [INFO] Executor
            special-topology-1-1415195688:[1 1] not alive
            2014-11-05 19:25:05 b.s.d.nimbus [INFO] Executor
            special-topology-1-1415195688:[3 3] not alive
            2014-11-05 19:25:05 b.s.d.nimbus [INFO] Executor
            special-topology-1-1415195688:[4 4] not alive
            2014-11-05 19:25:05 b.s.d.nimbus [INFO] Executor
            special-topology-1-1415195688:[1 1] not alive

            Why He can't start other worker on other machine

            Technical Specification :
            I am using storm-0.9.0.1 version.

            I have two machine
            nimbus : 192.168.1.13
            normal-supervisor : 192.168.1.13
            special-supervisor : 192.168.1.2

            I am waiting for user valuable guidance.
            Thank You In advance :)
-- Regards, 
            Swapnil K. Joshi
-- Regards, 
    Swapnil K. Joshi





--
Regards,
Swapnil K. Joshi

Reply via email to