[Linux-HA] Antw: Re: /usr/sbin/lrmadmin missing from cluster-glue
Lars Marowsky-Bree l...@suse.com schrieb am 25.01.2014 um 18:07 in Nachricht 20140125170730.gb9...@suse.de: On 2014-01-24T10:52:56, Tom Parker tpar...@cbnco.com wrote: Thanks Kristoffer. How is tuning done for lrm now? What do you want to tune? The LRM_MAX_CHILDREN setting is still (okay: again ;-), that was broken in one update) honored as before. Or you can use the node-action-limit property in the CIB to achieve the same, without setting environment variables; in case you don't like the automatic attempt at load dampening that pacemaker deploys. Talking on node-action-limit: I think I read in the syslog (not the best way to document changes) that the migration-limit parameter is obsoleted by node-action-limit in lastest SLES. Ist that correct? If so I think that's a poor decision, because a Xen live migration for a multi-GB-RAM-VM is a heavy weight process, while other actions are most likely much more lightweight, and VM migration probably does not benefit for parallel execution or multiple CPUs as it's very much I/O-heavy (not to say net-heavy). crmd[16709]: warning: cluster_option: Using deprecated name 'migration-limit' for cluster option 'node-action-limit' Regards, Ulrich Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] heartbeat failover
Hello Arnold, yes, I recently found out that the sync-rate was to high for our old firewall. That are two datacenters, and all traffic is routed through this firewall. I don't know exactly why, this is the concept somehow. Do you know how to force another ip address on the other side? In heartbeat I was able to say, that the clusterip is another one as on the other node. In corosync/pacemaker I can't find such an example. Best regards Björn -Ursprüngliche Nachricht- Von: linux-ha-boun...@lists.linux-ha.org [mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Arnold Krille Gesendet: Samstag, 25. Januar 2014 01:46 An: linux-ha@lists.linux-ha.org Betreff: Re: [Linux-HA] heartbeat failover On Thu, 23 Jan 2014 16:45:04 + bjoern.bec...@easycash.de wrote: Uhhh..I got the same configuration as the example config you sent me now. But I cause high cpu load on our cisco asa firewall.. I guess this traffic is not normal? snip When you want your cluster to repair failures _fast_, the components have to sync their state _fast_. So they have to talk a lot, not in terms of megabytes but in terms of small packages with low latency in submission. So, yes that traffic is normal. Why is there a firewall between your nodes on the network where the cluster traffic happens? Have fun, Arnold ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Antw: Re: /usr/sbin/lrmadmin missing from cluster-glue
On 2014-01-27T08:59:55, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: Talking on node-action-limit: I think I read in the syslog (not the best way to document changes) that the migration-limit parameter is obsoleted by node-action-limit in lastest SLES. Ist that correct? No. crmd[16709]: warning: cluster_option: Using deprecated name 'migration-limit' for cluster option 'node-action-limit' This message is misleading, sorry :-( Already fixed. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
[Linux-HA] Announcing docker resource-agent
Hey, I've created a docker resource agent that allows docker containers to be managed with pacemaker. The agent is up for review here, https://github.com/ClusterLabs/resource-agents/pull/370 Docker is a relatively new and fast moving project. I'd be surprised if anyone here is using it in production yet, but I'm sure some of you have investigated how it could be used. For review feedback, I'm not so much interested in a code review as much as a use-case analysis. How do you use or foresee yourself using docker containers in an HA environment, and does this agent work for your use-case? Thanks, -- Vossel ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
