You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a zookeeper quorum of 3 nodes and if any one of them goes down then secor dies even though there are still 2 of the 3 zookeeper nodes up. Also it won't start.
Just for the sake of testing I tried editing secor's list of zookeeper servers to remove that one and it still wouldn't start.
The text was updated successfully, but these errors were encountered:
orderedchaosdev
changed the title
Secor failing to start when zookeeper node is down
Secor failing to start/dying when zookeeper node is down
Mar 28, 2018
On Wed, Mar 28, 2018 at 11:44 AM, Sean Allen ***@***.***> wrote:
I have a zookeeper quorum of 3 nodes and if any one of them goes down then
secor dies even though there are still 2 of the 3 zookeeper nodes up.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#404>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHCX_4rm5wp992lcGKr7ULsZ7Hsv4pnFks5ti9oEgaJpZM4S_KUY>
.
Ok it turns out in the case where it wouldn't start there was something going on with zookeeper but somehow kafka kept running even with zookeeper acting up. Zookeeper recovered when I brought back its box and unfortunately the log rotation rotated the zookeeper logs out.
So I'm going to make a new ticket for another error, since I have no way to replicate the behavior of my original issue and it appears to have in fact been zookeeper.
I have a zookeeper quorum of 3 nodes and if any one of them goes down then secor dies even though there are still 2 of the 3 zookeeper nodes up. Also it won't start.
Just for the sake of testing I tried editing secor's list of zookeeper servers to remove that one and it still wouldn't start.
The text was updated successfully, but these errors were encountered: