Re: [Pacemaker] problem about move node from one cluster to another cluster
how does this fit the release schedule? The short answer is that it doesn't. The community generally does a pretty good job, heartbeat2 was a dead end that was put out of its misery years ago[1] and openais 0.80 was something like 5 years old when pacemaker started supporting it. Pacemaker 1.0 itself is almost 3 years old now iirc. But long term support will always be hole that enterprise vendors fill with products like sles, rhel and ubuntu LTS. With limited resources, projects need to choose their battles. We can't be everything to everyone, so we let the enterprise distress do what they do best while we concentrate on improving the core software. [1] there were also unique circumstances that necessitated killing hb2 early Sent from my iPad On 13 Oct 2010, at 13:37, Dan Frincu dfri...@streamwide.ro wrote: Hi, Yes, it sometime needs to be killed manually because the process hangs and the restart operation never seems to end. Yet another reason to upgrade. All, Question: given the fact that this type of software usually gets installed on a platform once and then usually goes into service for many years, on servers where downtime should be kept to a minimum (gee, that's why you use a cluster :)), how does this fit the release schedule? I mean, there are plenty of users out there with question related to Heartbeat 2, openais-0.8.0, and so on and so forth, some environments cannot be changed lightly, others, not at all, so what is the response to this feature doesn't work on that version of software?, upgrade? If so, at what interval (keeping in mind that you probably want the stable packages on your system)? I'm asking this because when I started working with openais, the latest version available was 0.8.0 on some SUSE repos that aren't available anymore. Regards, Dan jiaju liu wrote: Hi, Depending on the openais version (please mention it) Hi Thank you for your reply my openais version is openais-0.80.5-15.1 pacemaker version is pacemaker-1.0.5-4.1. I use restart but it does not work. I found it could not stop this behavior could happen, I've seen it as well, on openais-0.8.0. What I've done to fix it was to restart the openais process via /etc/init.d/openais restart. And then it worked, however, this was one of the reasons I updated the packages to the latest versions of corosync, pacemaker, etc. The tricky part was doing the migration procedure for upgrading production servers without service downtime, but that's another story. -- Dan FRINCU Systems Engineer CCNA, RHCE Streamwide Romania ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] problem about move node from one cluster to another cluster
--- 10年10月13日，周三, pacemaker-requ...@oss.clusterlabs.org pacemaker-requ...@oss.clusterlabs.org 写道： Send Pacemaker mailing list submissions to pacemaker@oss.clusterlabs.org To subscribe or unsubscribe via the World Wide Web, visit http://oss.clusterlabs.org/mailman/listinfo/pacemaker or, via email, send a message with subject or body 'help' to pacemaker-requ...@oss.clusterlabs.org You can reach the person managing the list at pacemaker-ow...@oss.clusterlabs.org When replying, please edit your Subject line so it is more specific than Re: Contents of Pacemaker digest... -- Message: 1 Date: Tue, 12 Oct 2010 21:04:36 +0300 From: Dan Frincu dfri...@streamwide.ro To: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] problem about move node from one clusterto another cluster Message-ID: 4cb4a334.3040...@streamwide.ro Content-Type: text/plain; charset=iso-8859-1; Format=flowed Hi, Depending on the openais version (please mention it) Hi Thank you for your reply my openais version is openais-0.80.5-15.1 pacemaker version is pacemaker-1.0.5-4.1. I use restart but it does not work. I found it could not stop this behavior could happen, I've seen it as well, on openais-0.8.0. What I've done to fix it was to restart the openais process via /etc/init.d/openais restart. And then it worked, however, this was one of the reasons I updated the packages to the latest versions of corosync, pacemaker, etc. The tricky part was doing the migration procedure for upgrading production servers without service downtime, but that's another story. Regards, Dan jiaju liu wrote: ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] problem about move node from one cluster to another cluster
Hi, Yes, it sometime needs to be killed manually because the process hangs and the restart operation never seems to end. Yet another reason to upgrade. All, Question: given the fact that this type of software usually gets installed on a platform once and then usually goes into service for many years, on servers where downtime should be kept to a minimum (gee, that's why you use a cluster :)), how does this fit the release schedule? I mean, there are plenty of users out there with question related to Heartbeat 2, openais-0.8.0, and so on and so forth, some environments cannot be changed lightly, others, not at all, so what is the response to this feature doesn't work on that version of software?, upgrade? If so, at what interval (keeping in mind that you probably want the stable packages on your system)? I'm asking this because when I started working with openais, the latest version available was 0.8.0 on some SUSE repos that aren't available anymore. Regards, Dan jiaju liu wrote: Hi, Depending on the openais version (please mention it) Hi Thank you for your reply my openais version is openais-0.80.5-15.1 pacemaker version is pacemaker-1.0.5-4.1. I use restart but it does not work. I found it could not stop this behavior could happen, I've seen it as well, on openais-0.8.0. What I've done to fix it was to restart the openais process via /etc/init.d/openais restart. And then it worked, however, this was one of the reasons I updated the packages to the latest versions of corosync, pacemaker, etc. The tricky part was doing the migration procedure for upgrading production servers without service downtime, but that's another story. -- Dan FRINCU Systems Engineer CCNA, RHCE Streamwide Romania ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] problem about move node from one cluster to another cluster
hi everybody I use command crm openais stop first to stop openais service and then use rm -rf /var/lib/heartbear/crm/* clear all information. then change multicast and start it in another cluster. the problem is sometimes it works I can use crm_mon command. and sometimes it doesn't work. I use service openais status. It shows Running. but I can not use crm_mon to connect to cluster. I found the reason may be directory /var/lib/heartbear/crm/ is empty. why??if I reboot ,it works again.WHY ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
