On Tue, Jul 30, 2013 at 2:52 PM, Kaushal M <kshlmster at gmail.com> wrote: > There are 2 workarounds to this for now, > 1. Enable a new feature on any volume in the cluster, which will bump up > the cluster op-version and allow it to probe the new peer. > 2. Remove the 'operating-version' line from /var/lib/glusterd/ > glusterd.info file on the new peer. This will cause the peer to start > operating at the minimum possible op-version, and it can then be probed. > > (Now that I've written this here, I need to document this some place, > probably the gluster wiki.) > Yes, please :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130730/12c4cda5/attachment.html>
