[Pacemaker] Simulating that a node is down.

[Jacobo García]

Thanks Andreas for your kind answer, I'll add this to my test battery.

Also, my other question, is it a good idea to close the corosync port?
Should corosync behave in a expected way? I am getting odd behaviors on
this one, but not sure if where to put the blame.

Thanks in advance.

Jacobo García López de Araujo
http://thebourbaki.com | http://twitter.com/clapkent


On Thu, Jul 11, 2013 at 8:39 PM, Andreas Mock <andreas.mock at web.de> wrote:

> 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****
>
> ** **
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130712/748b2b34/attachment.htm>