From ba24c7c3c29a41029a1762c238288d00b875ddef Mon Sep 17 00:00:00 2001 From: Kaushal M Date: Thu, 1 Aug 2013 10:55:19 +0530 Subject: doc: Add known issue about peer probe with op-version Change-Id: I152e5b63329540b65a86bc75f0a0c3a831761aaa Signed-off-by: Kaushal M Reviewed-on: http://review.gluster.org/5450 Reviewed-by: Vijay Bellur Tested-by: Vijay Bellur --- doc/release-notes/3.4.0.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'doc') diff --git a/doc/release-notes/3.4.0.md b/doc/release-notes/3.4.0.md index 40bb1efc5d9..de083b9479a 100644 --- a/doc/release-notes/3.4.0.md +++ b/doc/release-notes/3.4.0.md @@ -163,3 +163,16 @@ The G4S source is now in the separate git repository [here] - For Block Device translator based volumes open-behind xlator 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