My favorites | Sign in
Project Home Downloads
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 383: voldemort-admin-tool.sh does not always return from an --async stop of a list of jobs
1 person starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Project Member Reported by dremlok, Mar 29, 2012
What steps will reproduce the problem?
1. Start a rebalance job for a cluster
2. get the list of async jobs
3. stop the list of async jobs for a node

All jobs will stop, but the voldemort-admin-tool.sh will sometimes hang waiting on a particular job to stop and it may never return.

Running 0.95.1 for both server and admin tool.

[user@host voldemort]$ bin/voldemort-admin-tool.sh --async stop --async-id 0,13,14,15,16,17,18,19,20,21,22,25,26,27,28,29 --node 2 --url tcp://server1:6666
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,603 voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$ClientRequestSelectorManager] INFO Closed, exiting
[2012-03-29 19:33:33,607 voldemort.store.socket.clientrequest.ClientRequestExecutor] WARN No client associated with Socket[unconnected]
[2012-03-29 19:33:33,607 voldemort.store.socket.clientrequest.ClientRequestExecutor] INFO Closing remote connection from Socket[unconnected]
Stopping async id 0
Stopped async id 0
Stopping async id 13

It never progressed beyond job 13, but in another terminal if I do an --async get, I see no jobs running on any of the nodes.
Sign in to add a comment

Powered by Google Project Hosting