<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jul 30, 2013 at 2:52 PM, Kaushal M <span dir="ltr"><<a href="mailto:kshlmster@gmail.com" target="_blank">kshlmster@gmail.com</a>></span> wrote:<br>
<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr"><br>
There are 2 workarounds to this for now, <br>
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. <br>
2. Remove the 'operating-version' line from /var/lib/glusterd/<a href="http://glusterd.info" target="_blank">glusterd.info</a> 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. </p>
<p dir="ltr">(Now that I've written this here, I need to document this some place, probably the gluster wiki.)</p></blockquote><div><br></div><div>Yes, please :)<br> <br></div></div></div></div>