Description of problem: This bug is to track changes for upcall xlator options required to enable cache_invalidation and lease_locks support. Also this will track the changes required to handle cache_invalidation for all the fops which are missed out in the bug1200262.
In addition - will address below comments received as part of http://review.gluster.org/#/c/9535 - * skip cache_invalidation notifications only in case of internal Gluster fops. Can check using frame->root->pid.
REVIEW: http://review.gluster.org/9975 (Upcall: Added xlator options to enable cache-invalidation) posted (#1) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/9975 (Upcall: Added xlator options to enable cache-invalidation) posted (#2) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/9975 (Upcall: Added xlator options to enable cache-invalidation) posted (#3) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/9975 (Upcall: Added xlator options to enable cache-invalidation) posted (#4) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/9975 (Upcall: Added xlator options to enable cache-invalidation) posted (#5) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/9975 (Upcall: Added xlator options to enable cache-invalidation) posted (#6) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/9975 (Upcall: Added xlator options to enable cache-invalidation) posted (#7) for review on master by soumya k (skoduri)
COMMIT: http://review.gluster.org/9975 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 25f97b2788a33efcb0714ad639f8db380b864982 Author: Soumya Koduri <skoduri> Date: Tue Mar 24 10:30:31 2015 +0530 Upcall: Added xlator options to enable cache-invalidation Added two xlator options to enable cache-invalidation and set cache-invalidation-timeout. In addition, made few minor changes in the upcall processing code in gfapi. Change-Id: Ie0b32ca8348e34e3fe4f1e7df30cc925fa4aad31 BUG: 1200271 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/9975 Reviewed-by: Meghana M <mmadhusu> Reviewed-by: Kaleb KEITHLEY <kkeithle> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/10194 (Upcall: Handle missing fops in the upcall xlator) posted (#1) for review on master by soumya k (skoduri)
Internal gluster fops cannot be skipped for cache_invalidation as few of them like self-healing will result in data change.
REVIEW: http://review.gluster.org/10194 (Upcall: Handle missing fops in the upcall xlator) posted (#2) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/10194 (Upcall: Handle missing fops in the upcall xlator) posted (#3) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/10194 (eUpcall: Handle missing fops in the upcall xlator) posted (#4) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/10194 (eUpcall: Handle missing fops in the upcall xlator) posted (#5) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/10194 (eUpcall: Handle missing fops in the upcall xlator) posted (#6) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/10194 (Upcall: Handle missing fops in the upcall xlator) posted (#7) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/10194 (Upcall: Handle missing fops in the upcall xlator) posted (#8) for review on master by soumya k (skoduri)
REVIEW: http://review.gluster.org/10194 (Upcall: Handle missing fops in the upcall xlator) posted (#9) for review on master by soumya k (skoduri)
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user