Description of problem:
Currently, the callbacks, when generated, are sent to all the clients irrespective of whether they are interested or not. This needs to be addressed.
We can make use of IPC fop to notify upcall xlator whenever an application/clients starts polling or registers for upcall events.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: https://review.gluster.org/18863 (IPC: Add new IPC op to register/unregister upcall) posted (#1) for review on master by soumya k
REVIEW: https://review.gluster.org/18864 (md-cache: Use new IPC op to register/unreigster upcall) posted (#1) for review on master by soumya k
REVIEW: https://review.gluster.org/18866 (Upcall: Allow clients to register for cache-invalidation event) posted (#1) for review on master by soumya k
REVIEW: https://review.gluster.org/18865 (gfapi: Use new IPC op to register/unregister upcall event) posted (#1) for review on master by soumya k
Soumya, do you think we can close this? I see that these patches are not merged :-/ What should be our next step?
(In reply to Amar Tumballi from comment #5)
> Soumya, do you think we can close this? I see that these patches are not
> merged :-/ What should be our next step?
It will be good enhancement. This needs to be handled at different layers which I had posted patches for (IPC, md-cache, Upcall and gfapi). gfapi changes are addressed via a different patch - https://review.gluster.org/#/c/glusterfs/+/18349/ . Other patches (mostly trivial) can be revived and modified as per comments.
If there is anyone who is willing to take it forward I will be happy to guide. Or else it may take a little more while for me to work on this. We can close this bug and I will re-open incase I plan to fix it in future.
Thanks for the update Soumya. Will mark it as DEFERRED, and we can pick up when we get a chance.