Re: [ClusterLabs] Is it possible to downgrade feature-set in 2.1.6-8

2024-02-26 Thread vitaly
Thank you!
_Vitaly

> On 02/26/2024 10:28 AM EST Ken Gaillot  wrote:
> 
>  
> On Thu, 2024-02-22 at 08:05 -0500, vitaly wrote:
> > Hello. 
> > We have a product with 2 node clusters.
> > Our current version is using Pacemaker 2.1.4 the new version will be
> > using Pacemaker 2.1.6
> > During upgrade failure it is possible that one node will come up with
> > the new Pacemaker and work alone for a while.
> > Then old node would later come up and try to join the cluster.
> > This would fail due to the different feature-sets of the cluster
> > nodes. The older feature-set would not be able to join the newer
> > feature-set.
> >  
> > Question: 
> > Is is possible to force new node with Pacemaker 2.1.6 to use older
> > feature-set (3.15.0) for a while until second node is upgraded and is
> > able to work with Pacemaker 2.1.6?
> 
> No
> 
> >  
> > Thank you very much!
> > _Vitaly
> > 
> -- 
> Ken Gaillot 
> 
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> ClusterLabs home: https://www.clusterlabs.org/
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/


Re: [ClusterLabs] Is it possible to downgrade feature-set in 2.1.6-8

2024-02-26 Thread Ken Gaillot
On Thu, 2024-02-22 at 08:05 -0500, vitaly wrote:
> Hello. 
> We have a product with 2 node clusters.
> Our current version is using Pacemaker 2.1.4 the new version will be
> using Pacemaker 2.1.6
> During upgrade failure it is possible that one node will come up with
> the new Pacemaker and work alone for a while.
> Then old node would later come up and try to join the cluster.
> This would fail due to the different feature-sets of the cluster
> nodes. The older feature-set would not be able to join the newer
> feature-set.
>  
> Question: 
> Is is possible to force new node with Pacemaker 2.1.6 to use older
> feature-set (3.15.0) for a while until second node is upgraded and is
> able to work with Pacemaker 2.1.6?

No

>  
> Thank you very much!
> _Vitaly
> 
-- 
Ken Gaillot 

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/


[ClusterLabs] Is it possible to downgrade feature-set in 2.1.6-8

2024-02-22 Thread vitaly
Hello. 
We have a product with 2 node clusters.
Our current version is using Pacemaker 2.1.4 the new version will be using 
Pacemaker 2.1.6
During upgrade failure it is possible that one node will come up with the new 
Pacemaker and work alone for a while.
Then old node would later come up and try to join the cluster.
This would fail due to the different feature-sets of the cluster nodes. The 
older feature-set would not be able to join the newer feature-set.
 
Question:
Is is possible to force new node with Pacemaker 2.1.6 to use older feature-set 
(3.15.0) for a while until second node is upgraded and is able to work with 
Pacemaker 2.1.6?
 
Thank you very much!
_Vitaly___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/