Skip to content

Extend information in mgmtd log on mirror switching #59

@maksmarchenko

Description

@maksmarchenko

In mgmtd logs on BeeGFS 7 switching messages on mirror are :

(2) XNodeSync [Auto-offline] >> No state report received from metadata node for 180 seconds. Setting metadata node to offline. Metadata node ID: 401
(0) XNodeSync [Auto-offline] >> Tried to switch mirror group members, but refusing to switch due to secondary metadata node state. Current secondary metadata node ID: 401; secondary state: Offline / Good

and accordingly for successful switch:

(2) XNodeSync [Auto-offline] >> No state report received from metadata node for 191 seconds. Setting metadata node to offline. Metadata node ID: 1
(2) XNodeSync [Primary/secondary switch] >> Switching primary
and secondary target. Mirror group ID: 1

At current (8.x) mgmtd services in logs on mirror switching there are messages like

beegfs-mgmtd[]: Pushing exceeded quota IDs to some nodes failed. Request failures: 1, received non-success responses: 0
beegfs-mgmtd[]: message repeated 3 times: [ Pushing exceeded quota IDs to some nodes failed. Request failures: 1, received non-success responses: 0]
beegfs-mgmtd[]: A switchover was triggered for the following buddy groups: [(1, Meta)]
beegfs-mgmtd[]: Pushing exceeded quota IDs to some nodes failed. Request failures: 2, received non-success responses: 0
beegfs-mgmtd[]: message repeated 7 times: [ Pushing exceeded quota IDs to some nodes failed. Request failures: 2, received non-success responses: 0]

Additional information in mgmtd logs on BeeGFS 8 (may be even in same line) providing hints, which was primary or is primary now - after switch, and reason for switching - (which service is offline ) is very helpful in many cases.

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions