On 18/10/2013, at 10:12 PM, yusuke iida <yusk.i...@gmail.com> wrote:

> Hi, Andrew
> 
> Now, I am testing the configuration of one standby node and active node of 15.
> About 10 Dummy resources are started per node.
> 
> If all the nodes are started with this composition, before all the
> resources start, it will take the time for about 20 minutes.
> 
> And some resources have caused start timeout.
> probe is performed all at once by all the nodes at a start-up.
> The result is written in cib and synchronizes with all the nodes.
> This processing requires very high load.
> I think that timeout has occurred owing to it.

More than likely, yes.

> 
> I am very interested in whether this problem is solvable, if you use
> throttle created now.

I have been using it, I have found it more effective than batch-limit for 
bounding CPU usage and avoiding timeouts.
I would be interested to hear your feedback if you have the time to do some 
testing.

> When is throttle due to be merged into the repository of ClusterLabs?

It is queued up behind a compatibility patch that is needed for some changes I 
made to the pacemaker-remote wire protocol.

> 
> Best Regards,
> 
> -- 
> ----------------------------------------
> METRO SYSTEMS CO., LTD
> 
> Yusuke Iida
> Mail: yusk.i...@gmail.com
> ----------------------------------------
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker@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

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Pacemaker mailing list: Pacemaker@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

Reply via email to