You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three nodes of mariadb
node1: 1.1.1.21
node2: 1.1.1.22
node3: 1.1.1.23
[Problem scenario]
Problem time: 2023-02-28 15:50:15
Problem node: node2
Last restart and synced time: (node2) 2023-02-27 20:07:44 0 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 10872869)
Service was not restarted after 2023-02-27.
Last shift log:
(node1: 2023-02-28 14:08:26 0 [Note] WSREP: Restored state OPEN -> SYNCED (11343237)
node2: 2023-02-28 14:08:26 0 [Note] WSREP: Restored state OPEN -> SYNCED (11343237)
node3: 2023-02-28 14:08:26 0 [Note] WSREP: Restored state OPEN -> SYNCED (11343237)
)
[My analysis]
The problem may be related to the abnormal network environment.
[version]
Galera 25.3.33
Mariadb 10.3.30
[Background of the problem]
node1: 1.1.1.21
node2: 1.1.1.22
node3: 1.1.1.23
[Problem scenario]
Service was not restarted after 2023-02-27.
(node1: 2023-02-28 14:08:26 0 [Note] WSREP: Restored state OPEN -> SYNCED (11343237)
node2: 2023-02-28 14:08:26 0 [Note] WSREP: Restored state OPEN -> SYNCED (11343237)
node3: 2023-02-28 14:08:26 0 [Note] WSREP: Restored state OPEN -> SYNCED (11343237)
)
[My analysis]
[Problem]
node1 log
node1.txt
node2 log
node2.txt
node3 log
node3.txt
node2 error shows:
WSREP: exception from gcomm, backend must be restarted: evs::proto #202
exception from gcomm: mn.operational() == false #40
The text was updated successfully, but these errors were encountered: