[Pacemaker] problem about move node from one cluster to another cluster

[Dan Frincu]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101013/9573d51d/attachment-0002.htm>