[bug:1464639] Possible stale read in afr due to un-notified pending xattr change

[gluster-ant]

URL: https://bugzilla.redhat.com/1464639
Creator: pgurusid at redhat
Time: 20170624T04:14:46

Description of problem:

When the pending xattr is set, upcall is supposed to send
an upcall to the other clients, so that the other clients reset the
afr read subvolume (to not to point to the subvol with pending xattr set)
Currently, upcall is not sending any such invalidations.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

[gluster-ant]

Time: 20170624T04:15:46
bugzilla-bot at gluster.org commented:
REVIEW: https://review.gluster.org/17621 (upcall: Fix the condition check to filter afr pending xattrs change) posted (#1) for review on master by Poornima G (pgurusid@redhat.com)

[gluster-ant]

Time: 20170624T04:17:47
bugzilla-bot at gluster.org commented:
REVIEW: https://review.gluster.org/17621 (upcall: Fix the condition check to filter afr pending xattrs change) posted (#2) for review on master by Poornima G (pgurusid@redhat.com)

[gluster-ant]

Time: 20190614T08:46:31
atumball at redhat commented:
Any updates? Can this be revised? or closed as not relevant?

[stale]

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

[stale]

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.