Using a normal kill command (resulting in SIG_TERM) will allow the
process to shutdown properly, terminating everything in an orderly
manner. If for some reason you need to use kill -9, things won't be so
pretty. This shouldn't ever be necessary.
Distributions of flume will package it up as a service allowing you to
do "service flume start/stop" or similar, depending on your OS.
Cloudera's distribution is obviously the most well known. Under the
covers though these are doing the exact same thing(calling kill on the
flume process)
As to killing on multiple hosts, use a distribution or write your own
init.d script(which tracks the process id) and just stop/start the
service on all servers.
for i in $flume-hosts; do
ssh $i "service stop flume"
done
or something similar. Obviously it's going to depend on your
environment. I think clouderas manager gives a ui for this?
On 02/06/2013 05:19 AM, Yogi Nerella wrote:
Does anyone allow this in production to kill a process?
How can we manage killing the processes in multiple hosts?
Will there be any changes any new commands to stop the process in 1.4?
On Tue, Feb 5, 2013 at 12:16 PM, Harish Mandala
<[email protected] <mailto:[email protected]>> wrote:
Yes.
On Tue, Feb 5, 2013 at 3:14 PM, Yogi Nerella
<[email protected] <mailto:[email protected]>> wrote:
Hello,
I am not able to find a suitable command?
Is it just identifying the java application "Application" and
kill it?
Thanks,
Yogi
