Pranith Kumar Karampuri
2016-Jan-27 07:10 UTC
[Gluster-users] Determining Connected Client Version
On 01/27/2016 09:21 AM, Atin Mukherjee wrote:> > On 01/27/2016 07:21 AM, Vijay Bellur wrote: >> On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: >>> I'm trying to set a parameter on a volume, but unable to due to the >>> following message. I have a large number of connected clients and it's >>> likely that some clients have updated packages but haven't remounted the >>> volume. Is there an easier way to find the offending client? >>> >> You could grep for "accepted client from" in /var/log/glusterfs/bricks >> to get an idea of the versions of connected clients. > I had sent a patch [1] to improve the error message to indicate which > client is the culprit here. This is not the first time I've heard an > user complaining about it, so will try to get it in the release stream. > > Anyone up for review? > > [1] http://review.gluster.org/#/c/11831/This is definitely better than the state we have now. I looked at the patch. Looks fine. If you could resend the patch with BUG-id lets take it in. What would be even better is if we can enhance "gluster volume status clients" which prints the clients connected at the moment to also print the min,max op-versions so that the users can get the versions of all clients in one command. Pranith>> HTH, >> Vijay >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >> > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users
On 01/27/2016 12:40 PM, Pranith Kumar Karampuri wrote:> > > On 01/27/2016 09:21 AM, Atin Mukherjee wrote: >> >> On 01/27/2016 07:21 AM, Vijay Bellur wrote: >>> On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: >>>> I'm trying to set a parameter on a volume, but unable to due to the >>>> following message. I have a large number of connected clients and it's >>>> likely that some clients have updated packages but haven't remounted >>>> the >>>> volume. Is there an easier way to find the offending client? >>>> >>> You could grep for "accepted client from" in /var/log/glusterfs/bricks >>> to get an idea of the versions of connected clients. >> I had sent a patch [1] to improve the error message to indicate which >> client is the culprit here. This is not the first time I've heard an >> user complaining about it, so will try to get it in the release stream. >> >> Anyone up for review? >> >> [1] http://review.gluster.org/#/c/11831/ > > This is definitely better than the state we have now. I looked at the > patch. Looks fine. If you could resend the patch with BUG-id lets take > it in. > > What would be even better is if we can enhance "gluster volume status > clients" which prints the clients connected at the moment to also print > the min,max op-versions so that the users can get the versions of all > clients in one command.Yes doable. Actually I tried that earlier for the exact op-version but it seems like glusterd doesn't come to know about the exact op-version what client is running on. But having max and min op-version can certainly be done. Do you want to file an enhancement for this? ~Atin> > Pranith >>> HTH, >>> Vijay >>> >>> _______________________________________________ >>> Gluster-users mailing list >>> Gluster-users at gluster.org >>> http://www.gluster.org/mailman/listinfo/gluster-users >>> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users > >
On 01/27/2016 12:49 PM, Atin Mukherjee wrote:> > > On 01/27/2016 12:40 PM, Pranith Kumar Karampuri wrote: >> >> >> On 01/27/2016 09:21 AM, Atin Mukherjee wrote: >>> >>> On 01/27/2016 07:21 AM, Vijay Bellur wrote: >>>> On 01/26/2016 01:19 PM, Marc Eisenbarth wrote: >>>>> I'm trying to set a parameter on a volume, but unable to due to the >>>>> following message. I have a large number of connected clients and it's >>>>> likely that some clients have updated packages but haven't remounted >>>>> the >>>>> volume. Is there an easier way to find the offending client? >>>>> >>>> You could grep for "accepted client from" in /var/log/glusterfs/bricks >>>> to get an idea of the versions of connected clients. >>> I had sent a patch [1] to improve the error message to indicate which >>> client is the culprit here. This is not the first time I've heard an >>> user complaining about it, so will try to get it in the release stream. >>> >>> Anyone up for review? >>> >>> [1] http://review.gluster.org/#/c/11831/ >> >> This is definitely better than the state we have now. I looked at the >> patch. Looks fine. If you could resend the patch with BUG-id lets take >> it in. >> >> What would be even better is if we can enhance "gluster volume status >> clients" which prints the clients connected at the moment to also print >> the min,max op-versions so that the users can get the versions of all >> clients in one command. > Yes doable. Actually I tried that earlier for the exact op-version but > it seems like glusterd doesn't come to know about the exact op-version > what client is running on. But having max and min op-version can > certainly be done. Do you want to file an enhancement for this?I just now realized that glusterd's statedump captures this information which can be used for this case well.> > ~Atin >> >> Pranith >>>> HTH, >>>> Vijay >>>> >>>> _______________________________________________ >>>> Gluster-users mailing list >>>> Gluster-users at gluster.org >>>> http://www.gluster.org/mailman/listinfo/gluster-users >>>> >>> _______________________________________________ >>> Gluster-users mailing list >>> Gluster-users at gluster.org >>> http://www.gluster.org/mailman/listinfo/gluster-users >> >> > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >