summaryrefslogtreecommitdiffstats
path: root/extras/systemd/glustereventsd.service.in
diff options
context:
space:
mode:
authorPoornima G <pgurusid@redhat.com>2016-07-11 15:04:55 +0530
committerRaghavendra G <rgowdapp@redhat.com>2016-08-30 23:07:01 -0700
commit8f053f9d7270f1c6d50c0b3ab5d020503ceeb31a (patch)
tree754b2dbc815e8b0d619016b5d53f7e0acfae8c40 /extras/systemd/glustereventsd.service.in
parent55c255b27a99f027cb716800f8330f8faa4eb1f5 (diff)
md-cache: Register the list of xattrs with cache-invalidation
Issue: md-cache caches a specified list of xattrs, and when cache invalidation is enabled, it makes sense to recieve invalidation only when those xattrs are modified by other clients. But the current implementation of upcall is that, it will send invalidation when any of the on-disk xattrs is modified. Solution: md-cache sends a list of xattrs that it is interested in, to upcall by issuing an ipc(). The challenge here is to make sure everytime a brick goes offline and comes back up, the ipc() needs to be issued to the bricks. Hence ipc() is sent from md-cache every time there is a CHILD_UP/CHILD_MODIFIED event. TODO: There will be patches following, in cluster xlators, to implement ipc fop. Change-Id: I6efcf3df474f5ce6eabd3d6694c00c7bd89bc25d BUG: 1211863 Signed-off-by: Poornima G <pgurusid@redhat.com> Reviewed-on: http://review.gluster.org/15002 Smoke: Gluster Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Rajesh Joseph <rjoseph@redhat.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Prashanth Pai <ppai@redhat.com> Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
Diffstat (limited to 'extras/systemd/glustereventsd.service.in')
0 files changed, 0 insertions, 0 deletions