Query for available cluster nodes
Bug #1003908 reported by
Jay Janssen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Galera |
Fix Released
|
High
|
Alex Yurchenko |
Bug Description
I think it's important that we can query any cluster node to discover the state of all known cluster notes. Ideally, I'd like to see:
- all known cluster nodes
- what state they are in (active, offline, donor, etc.)
- their various addresses:
- wsrep communication address
- sst address
- wsrep node incoming address for client connections (maybe this is the most important).
-???
Certainly this amount of data makes the most sense in an I_S table, but a SHOW GLOBAL STATUS variable might be acceptable too (though with probably just a subset of info above).
Changed in galera: | |
importance: | Undecided → High |
status: | New → Confirmed |
assignee: | nobody → Alex Yurchenko (ayurchen) |
milestone: | none → 23.2.2 |
Changed in galera: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi Jay!
A few setbacks here:
1 - you can easily know only the nodes which are in the current component - i.e. nodes that see each other.
2 - only static node information (addresses and ports) can be passed via view callback, whereas node states can change any time and will require adding a number of new callbacks (which I frankly would prefer to avoid). So I'm wondering if querying node state directly would suffice.
3 - at the moment only incoming address information is globally available.
So, I can give you a list of incoming addresses by Monday, but the rest is quite a lot of work, involving protocol updates and, maybe, wsrep API changes.
How would you like to have your incoming list separated?