-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BW2 DR Failure Crashes Spawnpoint #22
Comments
After looking into this in more detail, there are deeper problems. If the DR fails, then reestablishing |
I've tried to make DR failures should be handled better. We still have the issue of the (usually local) agent failing as well, but some of this should be handled by restarting through Let's see how |
You should also try testing netsplits. I find the best way is to use iptables to drop all packets to/from the DR ip. Its distinct from DR failure in that the software doesn't get the TCP RST so it can behave quite differently |
Cool, thanks for the advice! Yeah, I'll add that to queue of stuff to do. |
When the Bosswave DR for its namespace fails, a spawnpoint daemon also fails.
We need to ensure that
spawnd
prints some informative warnings when this occurs, but continues operation.The text was updated successfully, but these errors were encountered: