Hi all, when stopping components of pinot (contro...
# general
s
Hi all, when stopping components of pinot (controller, broker, server) using admin script, sometimes component is not stopped and even is not logged.
Copy code
apache-pinot-0.9.3-bin/bin/pinot-admin.sh StopProcess -controller/-server/-broker
How do I know why it's not shutting down when executing stop command ? Also, is there any other way to stop pinot component safely? Thank you in advance.
m
Do you see anything in the logs?
s
@Mayank when executing stop server command , it shows like this. but server is still running . and it is not logged in pinot server log file.
m
Is this for production or local testing? Typically, in production, you’d use docker/k8s and that should be a more graceful way to handle startup/shutdown.
The StopProcess command is mostly for quick-start local setup. It looks for a file with *.pid and simply issues a kill command. My guess is that there is no *.pid file for your run where the command is looking at.
s
we are not using docker/k8s. we are using cluster consisting of multiple servers. is there other stop command for cluster? (not quick start)
p
We had this issue when we had server nodes which had previously hit an OutOfMemoryError but did not shutdown as a result. When you try a graceful shutdown nothing happens. The pattern I end up using for these scenarios is this: netstat -tulpn | grep LISTEN | grep <pinotPort> and then kill -9 the pid from above Could probably combine this with xargs into 1 command.