Hi,
Dante Garro wrote:
> Sunil, now I fall in count of messages are related to node 0, but the new is
> node 1 and does not care about the value I've setup allways says 14000 ms.
> Do this change your diagnostic?
Node1 start connection with node0, so you see the messages related to
node0 on node1
Sunil, now I fall in count of messages are related to node 0, but the new is
node 1 and does not care about the value I've setup allways says 14000 ms.
Do this change your diagnostic?
-Mensaje original-
De: Sunil Mushran [mailto:[EMAIL PROTECTED]
Enviado el: Jueves, 09 de Octubre de 2008
Yeah the cluster timeouts are not consistent. Update and restart
the cluster on the new node (or all nodes as the case might be).
Hint: cat /sys/kernel/config/cluster//idle_timeout_ms
to see the active heartbeat threshold.
Dante Garro wrote:
> Hi all, because problems with ocfs2 release of Debian
Hi all, because problems with ocfs2 release of Debian distribution decided
to remake my cluster replacing it by CentOS based installation.
Started replacing one of the nodes keeping the other working.
On this recently created node the following errors appears:
drbd0: Writing meta data super bloc
