On 2 Oct 2014, at 12:44 am, Digimer <[email protected]> wrote: > On 01/10/14 10:40 AM, Greg Woods wrote: >> I notice that the "network:ha-clustering:Stable" repo for CentOS 6 now >> contains Corosync 2.3.3-1 . I am currently running 1.4.1-17 . Is it safe to >> just run this update? Are there configuration changes I have to make in >> order for the new version to work? (If there is a document or wiki page >> describing how to convert from Corosync 1 to 2, I would be happy to be >> pointed to it). >> >> Thanks, >> --Greg > > Personally, I would not upgrade. If you do, you will want to test outside of > production first. > > Corosync needed cman to be a quorum provider in the 1.x series. In 2.x, it > became it's own quorum provider and cman was no longer needed. Last I heard > upstream, pacemaker on EL6 is only supported on corosync 1.4 + cman. I'm sure > you're not concerned about paid support, but it does mean that the corosync > 1.4 stack is much better tested on EL6 than 2.x is.
Also keep in mind that the version of pacemaker that comes with CentOS 6 wont work with this version of corosync You will need to rebuild it (or also obtain it from "network:ha-clustering:Stable" - which might not be automatic depending on what versions both have) > > If you really want a corosync v2+, then I would recommend switching to CentOS > 7. > > -- > Digimer > Papers and Projects: https://alteeve.ca/w/ > What if the cure for cancer is trapped in the mind of a person without access > to education? > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
