This repository was archived by the owner on Dec 4, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 85
Router mesh status check #3355
Comments
lulf
pushed a commit
to lulf/enmasse
that referenced
this issue
Oct 24, 2019
This adds a check for router mesh connectivity by querying the routers for its connected nodes in the router network. If the list of nodes does not contain the number of ready router pods, the address space status is set to false, and an error message is added to the status and in the log. Fixes EnMasseProject#3355
lulf
pushed a commit
that referenced
this issue
Oct 25, 2019
This adds a check for router mesh connectivity by querying the routers for its connected nodes in the router network. If the list of nodes does not contain the number of ready router pods, the address space status is set to false, and an error message is added to the status and in the log. Fixes #3355
lulf
pushed a commit
to lulf/enmasse
that referenced
this issue
Oct 28, 2019
This adds a check for router mesh connectivity by querying the routers for its connected nodes in the router network. If the list of nodes does not contain the number of ready router pods, the address space status is set to false, and an error message is added to the status and in the log. Fixes EnMasseProject#3355
lulf
pushed a commit
that referenced
this issue
Oct 28, 2019
This adds a check for router mesh connectivity by querying the routers for its connected nodes in the router network. If the list of nodes does not contain the number of ready router pods, the address space status is set to false, and an error message is added to the status and in the log. Fixes #3355
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Overview
A status check for the router mesh in the standard address space could uncover a situation where routers are not fully connected.
Design
The RouterStatusController class in address-space-controller which currently only checks connectors seems like an appropriate place to put this check.
The check should query all router pods for the address space and verify that they are all connected toeachother using the same mechanism as
qdstat -n
.The text was updated successfully, but these errors were encountered: