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
Hello, I have a problem with a 2-peer glusterfs cluster. Gluster starts correctly on both peers, but during testing (and I think in the future also in production) I found that as soon as I restart one peer, after booting up and running the command "gluster volume start <VOLUME_NAME>" on the peer that was restarted, on the other peer (the one that is running) there is no indication that the self-healing daemon (gluster volume status) is running, even though the process is visible as running. Could it be that we are not using the arbitrator?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, I have a problem with a 2-peer glusterfs cluster. Gluster starts correctly on both peers, but during testing (and I think in the future also in production) I found that as soon as I restart one peer, after booting up and running the command "gluster volume start <VOLUME_NAME>" on the peer that was restarted, on the other peer (the one that is running) there is no indication that the self-healing daemon (gluster volume status) is running, even though the process is visible as running. Could it be that we are not using the arbitrator?
Beta Was this translation helpful? Give feedback.
All reactions