[prev in list] [next in list] [prev in thread] [next in thread]
List: gluster-users
Subject: Re: [Gluster-users] Issue when upgrading from 3.6 to 3.7
From: Atin Mukherjee <amukherj () redhat ! com>
Date: 2016-07-27 14:07:04
Message-ID: CAGNCGH0eHJqc2FeQudjh8KQQmZ-cGGbWqnEpgoke_hAJBCWRBA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wed, Jul 27, 2016 at 5:05 PM, B.K.Raghuram <bkrram@gmail.com> wrote:
> Thanks a lot! Yes, I did upgrade to 3.7.13 but was unaware of the new
> cluster op-version. Could this incorrect op-version have been the cause for
> some of the peers being in the rejected state after an upgrade?
>
No, even if you run with a older op-version, things should not break. You'd
need to bump up the op-version only when you want to use the new features
been introduced with the same version.
> On Wed, Jul 27, 2016 at 3:49 PM, Manikandan Selvaganesh <
> mselvaga@redhat.com> wrote:
>
> > Hi,
> >
> > Sorry for the delay. Apparently, from your config files in the
> > /var/lib/glusterd/glusterd.info the operating-version
> > is still 30700. We have implemented quota-versioning in 3.7.6 and we
> > have another feature(enhancing quota
> > enable/disable performance improvements) implemented in 3.7.12.
> >
> > To use these features, you need to bump up the op version after the
> > upgrade by doing
> > 'gluster v set all cluster.op-version 30712(In case of 3.7.12). I guess
> > this would fix the problem you reported.
> > Let us know otherwise. If this does not fix the issue, please revert us
> > back with the logs.
> >
> > --
> > Regards,
> > Manikandan Selvaganesh.
> >
> >
> > On Wed, Jul 27, 2016 at 10:51 AM, Manikandan Selvaganesh <
> > mselvaga@redhat.com> wrote:
> >
> > > Hi Ram,
> > >
> > > Apologies. I was stuck on something else. I will update you within the
> > > EOD.
> > >
> > > On Wed, Jul 27, 2016 at 10:11 AM, B.K.Raghuram <bkrram@gmail.com> wrote:
> > >
> > > > Hi Manikandan,
> > > >
> > > > Did you have a chance to look at the glusterd config files? We've tried
> > > > a couple of times to upgrade from 3.6.1 and the vol info files never seems
> > > > to get a quota-version flag in it.. One of our installations is stuck at
> > > > the old version because of potential upgrade issues to 3.7.13.
> > > >
> > > > Thanks,
> > > > -Ram
> > > >
> > > > On Mon, Jul 25, 2016 at 6:40 PM, Manikandan Selvaganesh <
> > > > mselvaga@redhat.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > It would work fine with the upgraded setup on a fresh install. And
> > > > > yes, if quota-version is not present it would cause malfunctioning such as
> > > > > checksum issue, peer rejection and quota would not work properly. This
> > > > > quota-version is introduced recently which adds suffix to the quota related
> > > > > extended attributes.
> > > > >
> > > > > On Jul 25, 2016 6:36 PM, "B.K.Raghuram" <bkrram@gmail.com> wrote:
> > > > >
> > > > > > Manikandan,
> > > > > >
> > > > > > We just overwrote the setup with a fresh install and there I see the
> > > > > > quota-version in the volume info file. For the upgraded setup, I only \
> > > > > > have the /var/lib/glusterd, which I'm attaching. Once we recreate this, \
> > > > > > I'll send you the rest of the info.
> > > > > >
> > > > > > However, is there an issue if the quota-version is not being in the
> > > > > > info file? Will it cause the quota functionality to malfunction?
> > > > > >
> > > > > > On Mon, Jul 25, 2016 at 5:41 PM, Manikandan Selvaganesh <
> > > > > > mselvaga@redhat.com> wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > Could you please attach the vol files, log files and the output of
> > > > > > > gluster v info?
> > > > > > >
> > > > > > > On Mon, Jul 25, 2016 at 5:35 PM, Atin Mukherjee <amukherj@redhat.com
> > > > > > > > wrote:
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Jul 25, 2016 at 4:37 PM, B.K.Raghuram <bkrram@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Atin,
> > > > > > > > >
> > > > > > > > > Couple of quick questions about the upgrade and in general about
> > > > > > > > > the meaning of some of the parameters in the glusterd dir..
> > > > > > > > >
> > > > > > > > > - I dont see the quota-version in the volume info file post
> > > > > > > > > upgrade, so did the upgrade not go through properly?
> > > > > > > > >
> > > > > > > >
> > > > > > > > If you are seeing a check sum issue you'd need to copy the same
> > > > > > > > volume info file to that node where the checksum went wrong and then
> > > > > > > > restart glusterd service.
> > > > > > > > And yes, this looks like a bug in quota. @Mani - time to chip in :)
> > > > > > > >
> > > > > > > > - What does the op-version in the volume info file mean? Does this
> > > > > > > > > have any corelation with the cluster op-version? Does it change \
> > > > > > > > > with an upgrade?
> > > > > > > > >
> > > > > > > >
> > > > > > > > volume's op-version is different. This is basically used in
> > > > > > > > checking client's compatibility and it shouldn't change with an \
> > > > > > > > upgrade AFAIK and remember from the code.
> > > > > > > >
> > > > > > > >
> > > > > > > > > - A more basic question - should all peer probes always be done
> > > > > > > > > from the same node or can they be done from any node that is \
> > > > > > > > > already in the cluster? The reason I ask is when I tried to do what \
> > > > > > > > > was said in \
> > > > > > > > > http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
> > > > > > > > > the initial cluster was initiated from node A with 5 other peers. \
> > > > > > > > > Then post upgrade, node B which was in the cluster got a peer \
> > > > > > > > > rejected. So I deleted all the files except glusterd.info and then \
> > > > > > > > > did a peer probe of A from B. Then when I ran a peer status on A, \
> > > > > > > > > it only showed one node, B. Should I have probed B from A instead?
> > > > > > > > >
> > > > > > > >
> > > > > > > > peer probe can be done from any node in the trusted storage pool.
> > > > > > > > So that's really not the issue. Ensure you keep all your peer file \
> > > > > > > > contents through out the same (/var/lib/glusterd/peers) where as only \
> > > > > > > > self uuid differs and then restarting glusterd service should solve \
> > > > > > > > the problem.
> > > > > > > > >
> > > > > > > > > On Sat, Jul 23, 2016 at 10:48 AM, Atin Mukherjee <
> > > > > > > > > amukherj@redhat.com> wrote:
> > > > > > > > >
> > > > > > > > > > I am suspecting it to be new quota-version introduced in the
> > > > > > > > > > volume info file which may have resulted in a checksum mismatch \
> > > > > > > > > > resulting into peer rejection. But we can confirm it from log \
> > > > > > > > > > files and respective info file content.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Saturday 23 July 2016, B.K.Raghuram <bkrram@gmail.com> wrote:
> > > > > > > > > >
> > > > > > > > > > > Unfortunately, the setup is at a customer's place which is not
> > > > > > > > > > > remotely accessible. Will try and get it by early next week. \
> > > > > > > > > > > But could it just be a mismatch of the /var/lib/glusterd files?
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Jul 22, 2016 at 8:07 PM, Atin Mukherjee <
> > > > > > > > > > > amukherj@redhat.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Glusterd logs from all the nodes please?
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Friday 22 July 2016, B.K.Raghuram <bkrram@gmail.com> \
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > When we upgrade some nodes from 3.6.1 to 3.7.13, some of \
> > > > > > > > > > > > > the nodes give a peer status of "peer rejected" while some \
> > > > > > > > > > > > > dont. Is there a reason for this discrepency and will the \
> > > > > > > > > > > > > steps mentioned in \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > \
> > > > > > > > > > > > > work for this as well?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Just out of curiosity, why the line "Try the whole \
> > > > > > > > > > > > > procedure a couple more times if it doesn't work right \
> > > > > > > > > > > > > away." in the link above?
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Atin
> > > > > > > > > > > > Sent from iPhone
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Atin
> > > > > > > > > > Sent from iPhone
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > --Atin
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Gluster-users mailing list
> > > > > > > > Gluster-users@gluster.org
> > > > > > > > http://www.gluster.org/mailman/listinfo/gluster-users
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Manikandan Selvaganesh.
> > > > > > >
> > > > > >
> > > > > >
> > > >
> > >
> > >
> > > --
> > > Regards,
> > > Manikandan Selvaganesh.
> > >
> >
> >
> >
> >
> >
>
--
--Atin
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul \
27, 2016 at 5:05 PM, B.K.Raghuram <span dir="ltr"><<a \
href="mailto:bkrram@gmail.com" target="_blank">bkrram@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div dir="ltr">Thanks a lot! Yes, I did upgrade to \
3.7.13 but was unaware of the new cluster op-version. Could this incorrect op-version \
have been the cause for some of the peers being in the rejected state after an \
upgrade?<br></div></blockquote><div><br></div><div>No, even if you run with a older \
op-version, things should not break. You'd need to bump up the op-version only \
when you want to use the new features been introduced with the same \
version.<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"></div><div \
class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div \
class="gmail_quote">On Wed, Jul 27, 2016 at 3:49 PM, Manikandan Selvaganesh <span \
dir="ltr"><<a href="mailto:mselvaga@redhat.com" \
target="_blank">mselvaga@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 dir="ltr">Hi,<div><br></div><div>Sorry for the delay. \
Apparently, from your config files in the /var/lib/glusterd/<a \
href="http://glusterd.info" target="_blank">glusterd.info</a> the operating-version \
</div><div>is still 30700. We have implemented quota-versioning in 3.7.6 and we \
have another feature(enhancing quota</div><div>enable/disable performance \
improvements) implemented in 3.7.12.</div><div><br></div><div>To use these features, \
you need to bump up the op version after the upgrade by doing</div><div>'gluster \
v set all cluster.op-version 30712(In case of 3.7.12). I guess this would fix the \
problem you reported. </div><div>Let us know otherwise. If this does not fix the \
issue, please revert us back with the logs.</div><span><font \
color="#888888"><div><br></div><div>-- <br><div \
data-smartmail="gmail_signature"><div dir="ltr"><div>Regards,<br></div>Manikandan \
Selvaganesh.</div></div></div></font></span><div><div><div><br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 27, 2016 at 10:51 AM, \
Manikandan Selvaganesh <span dir="ltr"><<a href="mailto:mselvaga@redhat.com" \
target="_blank">mselvaga@redhat.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr">Hi Ram,<div><br></div><div>Apologies. I was stuck on something else. I will \
update you within the EOD.</div></div><div class="gmail_extra"><div><div><br><div \
class="gmail_quote">On Wed, Jul 27, 2016 at 10:11 AM, B.K.Raghuram <span \
dir="ltr"><<a href="mailto:bkrram@gmail.com" \
target="_blank">bkrram@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div><div><div>Hi Manikandan,<br><br></div>Did you have a chance to look at \
the glusterd config files? We've tried a couple of times to upgrade from 3.6.1 \
and the vol info files never seems to get a quota-version flag in it.. One of our \
installations is stuck at the old version because of potential upgrade issues to \
3.7.13.<br><br></div>Thanks,<br></div>-Ram<br></div><div><div><div \
class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 25, 2016 at 6:40 PM, \
Manikandan Selvaganesh <span dir="ltr"><<a href="mailto:mselvaga@redhat.com" \
target="_blank">mselvaga@redhat.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><p \
dir="ltr">Hi,</p> <p dir="ltr">It would work fine with the upgraded setup on a fresh \
install. And yes, if quota-version is not present it would cause malfunctioning such \
as checksum issue, peer rejection and quota would not work properly. This \
quota-version is introduced recently which adds suffix to the quota related extended \
attributes.</p><div><div> <div class="gmail_extra"><br><div class="gmail_quote">On \
Jul 25, 2016 6:36 PM, "B.K.Raghuram" <<a href="mailto:bkrram@gmail.com" \
target="_blank">bkrram@gmail.com</a>> wrote:<br type="attribution"><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div><div>Manikandan,<br><br></div>We just overwrote the setup with a fresh \
install and there I see the quota-version in the volume info file. For the upgraded \
setup, I only have the /var/lib/glusterd, which I'm attaching. Once we recreate \
this, I'll send you the rest of the info.<br><br></div>However, is there an issue \
if the quota-version is not being in the info file? Will it cause the quota \
functionality to malfunction?<br></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, Jul 25, 2016 at 5:41 PM, Manikandan Selvaganesh <span \
dir="ltr"><<a href="mailto:mselvaga@redhat.com" \
target="_blank">mselvaga@redhat.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr">Hi,<div><br></div><div>Could you please attach the vol files, log files and \
the output of gluster v info?</div><div class="gmail_extra"><br><div \
class="gmail_quote"><div><div>On Mon, Jul 25, 2016 at 5:35 PM, Atin Mukherjee <span \
dir="ltr"><<a href="mailto:amukherj@redhat.com" \
target="_blank">amukherj@redhat.com</a>></span> wrote:<br></div></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div \
dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Mon, Jul \
25, 2016 at 4:37 PM, B.K.Raghuram <span dir="ltr"><<a \
href="mailto:bkrram@gmail.com" target="_blank">bkrram@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><div><div><div>Atin,<br><br></div>Couple of quick questions about the \
upgrade and in general about the meaning of some of the parameters in the glusterd \
dir..<br><br></div><div>- I dont see the quota-version in the volume info file post \
upgrade, so did the upgrade not go through properly? \
<br></div></div></div></div></blockquote><div><br></div></span>If you are seeing a \
check sum issue you'd need to copy the same volume info file to that node where \
the checksum went wrong and then restart glusterd service.<br><div>And yes, this \
looks like a bug in quota. @Mani - time to chip in :)<br><br> </div><span><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><div><div></div>- What does the op-version in the volume info file \
mean? Does this have any corelation with the cluster op-version? Does it change with \
an upgrade?<br></div></div></div></blockquote><div><br></div></span><div>volume's \
op-version is different. This is basically used in checking client's \
compatibility and it shouldn't change with an upgrade AFAIK and remember from the \
code.<br> <br></div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><div></div>- A more basic question - should all peer probes always be \
done from the same node or can they be done from any node that is already in the \
cluster? The reason I ask is when I tried to do what was said in <a \
href="http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/" \
target="_blank">http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/</a> \
the initial cluster was initiated from node A with 5 other peers. Then post upgrade, \
node B which was in the cluster got a peer rejected. So I deleted all the files \
except <a href="http://glusterd.info" target="_blank">glusterd.info</a> and then did \
a peer probe of A from B. Then when I ran a peer status on A, it only showed one \
node, B. Should I have probed B from A \
instead?<br></div></div></blockquote><div><br></div></span><div> peer probe can be \
done from any node in the trusted storage pool. So that's really not the issue. \
Ensure you keep all your peer file contents through out the same \
(/var/lib/glusterd/peers) where as only self uuid differs and then restarting \
glusterd service should solve the problem.<br></div><span><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div></div></div><div><div><div class="gmail_extra"><br><div \
class="gmail_quote">On Sat, Jul 23, 2016 at 10:48 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:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I \
am suspecting it to be new quota-version introduced in the volume info file which \
may have resulted in a checksum mismatch resulting into peer rejection. But we can \
confirm it from log files and respective info file \
content.<div><div><span></span><br><br>On Saturday 23 July 2016, B.K.Raghuram <<a \
href="mailto:bkrram@gmail.com" target="_blank">bkrram@gmail.com</a>> \
wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
dir="ltr">Unfortunately, the setup is at a customer's place which is not remotely \
accessible. Will try and get it by early next week. But could it just be a mismatch \
of the /var/lib/glusterd files? <br></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Fri, Jul 22, 2016 at 8:07 PM, Atin Mukherjee <span \
dir="ltr"><<a>amukherj@redhat.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Glusterd \
logs from all the nodes please?<div><div><span></span><br><br>On Friday 22 July 2016, \
B.K.Raghuram <<a>bkrram@gmail.com</a>> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div>When we upgrade some nodes from 3.6.1 to 3.7.13, some of the nodes \
give a peer status of "peer rejected" while some dont. Is there a reason \
for this discrepency and will the steps mentioned in <a \
href="http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/" \
target="_blank">http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/</a> \
work for this as well?<br><br></div>Just out of curiosity, why the line "Try the \
whole procedure a couple more times if it doesn't work right away." in the \
link above?<br></div> </blockquote><br><br></div></div><span><font color="#888888">-- \
<br>Atin<br>Sent from iPhone<br> </font></span></blockquote></div><br></div>
</blockquote><br><br>-- <br>Atin<br>Sent from iPhone<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></span></div><span><font color="#888888"><br><br \
clear="all"><br>-- <br><div data-smartmail="gmail_signature"><div \
dir="ltr"><div><br></div>--Atin<br></div></div> </font></span></div></div>
<br></div></div>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" \
target="_blank">Gluster-users@gluster.org</a><br> <a \
href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" \
target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><span><font \
color="#888888"><br></font></span></blockquote></div><span><font \
color="#888888"><br><br clear="all"><div><br></div>-- <br><div \
data-smartmail="gmail_signature"><div dir="ltr"><div>Regards,<br></div>Manikandan \
Selvaganesh.<br></div></div> </font></span></div></div>
</blockquote></div><br></div>
</blockquote></div></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br \
clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div \
data-smartmail="gmail_signature"><div dir="ltr"><div>Regards,<br></div>Manikandan \
Selvaganesh.<br></div></div> </font></span></div>
</blockquote></div><br><br clear="all"><div><br></div><div \
data-smartmail="gmail_signature"><div dir="ltr"><br></div></div> \
</div></div></div></div> </blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div \
class="gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr"><div><br></div>--Atin<br></div></div> </div></div>
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic