From 8565d383a11d52b2db649f0c277d6f9ef1e87623 Mon Sep 17 00:00:00 2001 From: Kaushal M Date: Wed, 28 Aug 2013 17:16:03 +0530 Subject: glusterd: Allow bumping down a peer's op-version during probe Backport of http://review.gluster.org/5715 Earlier, a peer running a higher op-version couldn't be probed into a cluster running at a lower op-version. This created issues when trying to expand an upgraded cluster. This patch changes this behaviour. The cluster no longer rejects a peer being probed if its op-version is higher than the cluster op-version. The peer will reduce its op-version if it doesn't have any volumes. If the peer contains volumes and needs to reduce its op-version, it fails the handshake and the probe fails. BUG: 1005038 Change-Id: Iabe790a9f826a4ac63d379eeeba01efcfef01f4d Signed-off-by: Kaushal M Reviewed-on: http://review.gluster.org/5834 Tested-by: Gluster Build System Reviewed-by: Vijay Bellur --- doc/release-notes/3.4.0.md | 13 ------------- 1 file changed, 13 deletions(-) (limited to 'doc/release-notes/3.4.0.md') diff --git a/doc/release-notes/3.4.0.md b/doc/release-notes/3.4.0.md index 15aff92fa..b906e6a94 100644 --- a/doc/release-notes/3.4.0.md +++ b/doc/release-notes/3.4.0.md @@ -165,16 +165,3 @@ More details can be found [here] - For Block Device translator based volumes open-behind translator at the client side needs to be disabled. - -- More information on this can be found in this mailing list - [post](http://www.gluster.org/pipermail/gluster-users/2013-July/036750.html) - A freshly installed peer cannot be probed into a freshly upgraded cluster. - This is a limitation brought about by the introduction of op-versions. - There are two ways to workaround this issue, - * enable any new feature (for eg. open-behind) on a volume in the cluster, - and then perform the probe. - Or, if you don't want to enable any new features - * delete the 'operating-version' line from /var/lib/glusterd/glusterd.info - on the newly installed peer and restart glusterd on the peer. - If the file doesn't exist (because of lazy uuid generation), try to probe - the peer from the cluster (which will fail) to get the file created. -- cgit