<div dir="ltr">Thanks! That will work.<div>Not actually a "user-friendly" approach, but at least scriptable :)</div></div><br><div class="gmail_quote"><div dir="ltr">ср, 13 июл. 2016 г. в 8:41, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>OK, so we already have this in glusterd's statedump. If you execute kill -SIGUSR1 $(pidof glusterd) you will get a glusterd statedump file with naming convention as glusterdump.<pid of glusterd>.dump. <time instance> in /var/run/gluster. This file would contain glusterd.max-op-version value under [xlator.glusterd.priv] section.<br><br></div>HTH,<br></div><div class="gmail_extra"></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 13, 2016 at 6:11 AM, Atin Mukherjee <span dir="ltr"><<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br><br>On Wednesday 13 July 2016, Pavel Malyshev <<a href="mailto:p.malishev@gmail.com" target="_blank">p.malishev@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hello!<br><br></div>I use gluster for quite a long time and even survived a bunch of upgrades..<br></div>Each time I upgrade, since "op-version" was introduced I scratch my head and google a bit to find out which "op-version" should I set to my cluster.<br></div>I tried to convert current gluster package version to op-version, like 3.7.1 to 30701, but it didn't work with 3,5&3.6 patches and some 3.7 patches (like 3.7.9, 3.7.11, etc).<br>Last few times I had to download latest gluster sources and grep for 'GD_OP_VERSION' to find out the new value, which is not user friendly (or completely user unfriendly?).<br></div>I have an automated system to deploy and upgrade gluster clusters, but till now I had to spend precious time to find out actual version value and set it manually...<br><br></div><div>So my question is there any way to get the maximum supported op-version of installed glusterd daemon (not cluster version) via cli?<br></div></div></blockquote><div><br></div></div></div><div>No, we dont have. I think we can capture this in<span></span> glusterd's statedump.</div><span><font color="#888888"><br><br>-- <br>Atin<br>Sent from iPhone<br>
</font></span></blockquote></div><br><br clear="all"><br></div><div class="gmail_extra">-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><br></div>--Atin<br></div></div>
</div></blockquote></div>