Skip to content
This repository was archived by the owner on Nov 22, 2022. It is now read-only.
This repository was archived by the owner on Nov 22, 2022. It is now read-only.

Restarting error in node1 #5

@hyeonsangjeon

Description

@hyeonsangjeon

If I stop the node1(wsrep-new-cluster), and then start node1 container again, node1 will have a desync for this node. Do you know how to solve this?

2019-05-14 10:32:31 140255967299520 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
2019. 5. 14. 오전 10:32:31 at gcomm/src/pc.cpp:connect():158
2019. 5. 14. 오전 10:32:312019-05-14 10:32:31 140255967299520 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208: Failed to open backend connection: -110 (Connection timed out)
2019. 5. 14. 오전 10:32:312019-05-14 10:32:31 140255967299520 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1404: Failed to open channel 'maria_cluster' at 'gcomm://node2-dl-mariadb,node3-dl-mariadb': -110 (Connection timed out)
2019. 5. 14. 오전 10:32:312019-05-14 10:32:31 140255967299520 [ERROR] WSREP: gcs connect failed: Connection timed out
2019. 5. 14. 오전 10:32:312019-05-14 10:32:31 140255967299520 [ERROR] WSREP: wsrep::connect(gcomm://node2-dl-mariadb,node3-dl-mariadb) failed: 7
2019. 5. 14. 오전 10:32:312019-05-14 10:32:31 140255967299520 [ERROR] Aborting

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