Discussion:
Issue when upgrading from 3.6 to 3.7
(too old to reply)
B.K.Raghuram
2016-07-22 14:31:21 UTC
Permalink
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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 Mukherjee
2016-07-22 14:37:00 UTC
Permalink
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
B.K.Raghuram
2016-07-23 04:06:23 UTC
Permalink
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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 Mukherjee
2016-07-23 05:18:14 UTC
Permalink
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.
Post by B.K.Raghuram
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
B.K.Raghuram
2016-07-25 11:07:30 UTC
Permalink
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?
- 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?
- 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?
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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 Mukherjee
2016-07-25 12:05:47 UTC
Permalink
Post by B.K.Raghuram
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
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
Manikandan Selvaganesh
2016-07-25 12:11:44 UTC
Permalink
Hi,

Could you please attach the vol files, log files and the output of gluster
v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this have
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
B.K.Raghuram
2016-07-25 13:06:35 UTC
Permalink
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?
Post by Manikandan Selvaganesh
Hi,
Could you please attach the vol files, log files and the output of gluster
v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this have
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
Manikandan Selvaganesh
2016-07-25 13:10:49 UTC
Permalink
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.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
Hi,
Could you please attach the vol files, log files and the output of
gluster v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this have
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
B.K.Raghuram
2016-07-27 04:41:33 UTC
Permalink
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
Post by Manikandan Selvaganesh
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.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
Hi,
Could you please attach the vol files, log files and the output of
gluster v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this have
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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?
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
Manikandan Selvaganesh
2016-07-27 05:21:05 UTC
Permalink
Hi Ram,

Apologies. I was stuck on something else. I will update you within the EOD.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
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.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
Hi,
Could you please attach the vol files, log files and the output of
gluster v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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 <
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
--
Regards,
Manikandan Selvaganesh.
Manikandan Selvaganesh
2016-07-27 10:19:25 UTC
Permalink
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 <
Post by Manikandan Selvaganesh
Hi Ram,
Apologies. I was stuck on something else. I will update you within the EOD.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
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.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
Hi,
Could you please attach the vol files, log files and the output of
gluster v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
On Sat, Jul 23, 2016 at 10:48 AM, Atin Mukherjee <
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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 <
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
--
Regards,
Manikandan Selvaganesh.
B.K.Raghuram
2016-07-27 11:35:47 UTC
Permalink
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?
Post by Manikandan Selvaganesh
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 <
Post by Manikandan Selvaganesh
Hi Ram,
Apologies. I was stuck on something else. I will update you within the EOD.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
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.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
Hi,
Could you please attach the vol files, log files and the output of
gluster v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
On Sat, Jul 23, 2016 at 10:48 AM, Atin Mukherjee <
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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 <
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
--
Regards,
Manikandan Selvaganesh.
Atin Mukherjee
2016-07-27 13:55:04 UTC
Permalink
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
On Wed, Jul 27, 2016 at 3:49 PM, Manikandan Selvaganesh <
Post by Manikandan Selvaganesh
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 <
Post by Manikandan Selvaganesh
Hi Ram,
Apologies. I was stuck on something else. I will update you within the EOD.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
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.
Post by B.K.Raghuram
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 <
Post by Manikandan Selvaganesh
Hi,
Could you please attach the vol files, log files and the output of
gluster v info?
Post by Atin Mukherjee
Post by B.K.Raghuram
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.
- What does the op-version in the volume info file mean? Does this
Post by B.K.Raghuram
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.
Post by B.K.Raghuram
- 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.
Post by B.K.Raghuram
On Sat, Jul 23, 2016 at 10:48 AM, Atin Mukherjee <
Post by Atin Mukherjee
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.
Post by B.K.Raghuram
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 <
Post by Atin Mukherjee
Glusterd logs from all the nodes please?
Post by B.K.Raghuram
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
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
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
http://www.gluster.org/mailman/listinfo/gluster-users
--
Regards,
Manikandan Selvaganesh.
--
Regards,
Manikandan Selvaganesh.
--
--Atin
Continue reading on narkive:
Loading...