[Pacemaker] Simulating that a node is down.

[Andreas Mock]

Hi Jacobo,

 

one very interesting thing is missing.

Overload the node. Make a programm/script which generates

many IO-operations, many flushes and meanwhile requesting

more and more memory from the OS until swapping begins.

Ohhh, yes, swapping and IO is nice…

 

…then you can prove your monitor and stop action timeouts…  ;-)

 

Best regards

Andreas Mock

 

 

Von: Jacobo García [mailto:jacobo.garcia at gmail.com] 
Gesendet: Donnerstag, 11. Juli 2013 19:14
An: pacemaker at oss.clusterlabs.org
Betreff: [Pacemaker] Simulating that a node is down.

 

Hello,

 

I am looking for different ways of testing that a node is down. I am finding a strange behavior with one of them (closing with IPtables the UDP communication port). I would like to know if closing the port is a recommended way of achieving my testing purposes. 

 

Also I would like to know other ways of testing apart from the ones compiled in the list below:

 

1.     Stopping corosync.

2.     Shutting down the node.

3.     Shutting down the eth0 interface.

4.     Killing corosync process.

5.     Closing the corosync communication port.

Thanks,




Jacobo García López de Araujo

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130711/0afd4a8a/attachment.htm>