Hi Udo,
This issue your having aside for a moment;
How many hosts in a cluster sharing the GFS2 file system? I had issues
scaling more then 2 nodes because of locking performance problems. I
imagine your IO is horrible as well, as in a few MB/s. I used CLVM
instead of mounting a GFS2 file sys
Hi Udo,
Perhaps not relevant, but check host 65, error message being:
2019-05-07 07:09:19,718 DEBUG [c.c.a.t.Request] (AgentManager-Handler-15:null)
(logid:) Seq 65-6444932541743890440: Processing: { Ans: , MgmtId:
101543520292, via: 65, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"res
Hi Adrian,
yes it was. I think below message results from minimizing the CS Cluster to
have a better overview over the agent log files.
I apologize for that.
See
https://www.file-upload.net/download-13596521/management-server.log.html
where the cluster is fully populated again with 20 hosts
Hi!
Yes, we are still on 4.9.2
Yes we have a pacemaker cluster which is used to mount a GFS2 shared
filesystem. No CLVM.
Storage is mounted fine, Fencing is enabled and working.
We have single CS management server.
Here you'll find the log from fresh start until ssvm alerts:
https://www.file
