2018-03-20 16:22:30 UTC - Karthik Palanivelu: Hi all, I am trying to test the geo-replication using two standalone installations as suggested by @Matteo Merli . I am getting Not enough non-faulty bookies available. I understand bookies write copy is configured as 1 and I see a error on server startup as Triggering Shutdown of Bookie-3181 with Exit code 4. When stopping pulsar I kill the process. Please let me know how to gracefully shutdown and how to fix this issue ---- 2018-03-20 16:24:36 UTC - Matteo Merli: Hi, do you see any other warn/error messages in the logs? ---- 2018-03-20 17:02:44 UTC - Karthik Palanivelu: I see “Couldn’t register bookie with zookeeper, shutting down” ---- 2018-03-20 17:03:39 UTC - Matteo Merli: Are the 2 standalone processes running on same machine or different machines? ---- 2018-03-20 17:03:41 UTC - Karthik Palanivelu: Node exists for /ledgers/available/127.0.0.1:3181 ---- 2018-03-20 17:04:01 UTC - Karthik Palanivelu: I am just running only one to start with ---- 2018-03-20 17:04:29 UTC - Karthik Palanivelu: I am hardening my AWS script by killing and starting back ---- 2018-03-20 17:04:36 UTC - Karthik Palanivelu: I hit this error ---- 2018-03-20 17:06:51 UTC - Matteo Merli: I see, the issue is probably related to the fact that the the bookie registration z-node was not cleaned up from previous execution, so it has to wait until the previous session expires ---- 2018-03-20 17:09:23 UTC - Karthik Palanivelu: Is there a way to gracefully stop standalone? And any recommendations to expire the previous session? What is the default session timeout? ---- 2018-03-20 17:10:42 UTC - Matteo Merli: sending `SIGINT` or `SIGQUIT` should work ---- 2018-03-20 17:11:07 UTC - Matteo Merli: (`SIGINT` for sure, tried that a huge number of times on console) ---- 2018-03-20 17:32:35 UTC - Karthik Palanivelu: Oh, it worked ---- 2018-03-20 17:32:41 UTC - Karthik Palanivelu: Thank you ---- 2018-03-21 08:57:14 UTC - Piotr: @Piotr has joined the channel ---- 2018-03-21 09:00:28 UTC - Piotr: Hi there. Is PulsarAdmin not available in the current release of the Java client? I can see it in the github repo but not in the maven artifact ---- 2018-03-21 09:08:32 UTC - Ivan Kelly: <http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client-admin%7C1.22.0-incubating%7Cjar> ? ----
