database status and watch: display and noise findings (B9-B13) #109

Open
opened 2026-10-08 21:03:57 -03:00 by marcos-mendez · 0 comments
marcos-mendez commented 2026-10-08 21:03:57 -03:00 (Migrated from github.com)

Found in the real-node test of the MariaDB pair, keel 0.23.3. All LOW.

ID Severity Problem Output
B9 Low keel database status line "the primary's address" always names the other member, also on the primary. db-1 as primary: the primary's address: fd11:a58a:88ef:0:cd53:dda9:f0cb:b889 (that is db-2)
B10 Low keel database status on the replica shows an empty "GTID IO position" right after the seed. TLS Yes; GTID IO position (empty) while Gtid_IO_Pos: 0-388044305-16
B11 Low semi-synchronous ... N not: commits applied while the node was a replica, or with no replica, are counted as "not acknowledged". It reads as lost acks. 36 commits acknowledged, 112 not 5 s after the planned promote
B12 Low keel 0.23.3 enables keel-database-watch.timer on nodes with no database; it logs "skipped, unmet condition" every 30 s. keel-database-watch.service ... skipped, unmet condition check ConditionPathExists=/var/lib/keel/database
B13 Low web-2 warns at every keel command that overlays.vip is not declared (spec not written out after the chain gained vip). Known behavior, but web-2 still has it. Warning: /etc/keel/instance.yaml: overlays.vip: not declared (default: disabled) ...

Evidence: Keel-Linux/handbook#60, docs/evidence/2026-10-08-mariadb-pair-real.md.

Found in the real-node test of the MariaDB pair, keel 0.23.3. All LOW. | ID | Severity | Problem | Output | |---|---|---|---| | B9 | Low | `keel database status` line "the primary's address" always names the other member, also on the primary. | db-1 as primary: `the primary's address: fd11:a58a:88ef:0:cd53:dda9:f0cb:b889` (that is db-2) | | B10 | Low | `keel database status` on the replica shows an empty "GTID IO position" right after the seed. | `TLS Yes; GTID IO position ` (empty) while `Gtid_IO_Pos: 0-388044305-16` | | B11 | Low | `semi-synchronous ... N not`: commits applied while the node was a replica, or with no replica, are counted as "not acknowledged". It reads as lost acks. | `36 commits acknowledged, 112 not` 5 s after the planned promote | | B12 | Low | keel 0.23.3 enables `keel-database-watch.timer` on nodes with no database; it logs "skipped, unmet condition" every 30 s. | `keel-database-watch.service ... skipped, unmet condition check ConditionPathExists=/var/lib/keel/database` | | B13 | Low | web-2 warns at every keel command that `overlays.vip` is not declared (spec not written out after the chain gained `vip`). Known behavior, but web-2 still has it. | `Warning: /etc/keel/instance.yaml: overlays.vip: not declared (default: disabled) ...` | Evidence: Keel-Linux/handbook#60, docs/evidence/2026-10-08-mariadb-pair-real.md.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Keel-Linux/keel#109
No description provided.