database status and watch: display and noise findings (B9-B13) #109
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/keel#109
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found in the real-node test of the MariaDB pair, keel 0.23.3. All LOW.
keel database statusline "the primary's address" always names the other member, also on the primary.the primary's address: fd11:a58a:88ef:0:cd53:dda9:f0cb:b889(that is db-2)keel database statuson the replica shows an empty "GTID IO position" right after the seed.TLS Yes; GTID IO position(empty) whileGtid_IO_Pos: 0-388044305-16semi-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 not5 s after the planned promotekeel-database-watch.timeron nodes with no database; it logs "skipped, unmet condition" every 30 s.keel-database-watch.service ... skipped, unmet condition check ConditionPathExists=/var/lib/keel/databaseoverlays.vipis not declared (spec not written out after the chain gainedvip). 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.