diff options
author | Poornima G <pgurusid@redhat.com> | 2016-12-26 16:26:49 +0530 |
---|---|---|
committer | Raghavendra G <rgowdapp@redhat.com> | 2017-01-08 21:12:48 -0800 |
commit | 3fcd790d9ca01a95026026d64385c52b5476174d (patch) | |
tree | ec7ba4967ef1def08f9b55af20a4e398f31bbea5 /xlators/mgmt/glusterd/src/glusterd-scrub-svc.c | |
parent | 521c55c53bd42bfdcc0919019ee81c81305382a2 (diff) |
md-cache: Cache updated as a part of invalidate should not update time
Currently when a invalidate happens we update the cache along with
the cache time. The problem with this is, upcall doesn't update the
last access time of a client when an invalidation is sent, thus resulting
in a timewindow where the md-cache has cached, but the upcall is unaware
and hence upcall will not further invalidate the cache(unless a fop is sent
from the same client, and upcall updates its database to reflect the same)
Change-Id: Ibceb8d2fc360582752846bbf7fd59697d5424754
Signed-off-by: Poornima G <pgurusid@redhat.com>
Reviewed-on: http://review.gluster.org/16295
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
Diffstat (limited to 'xlators/mgmt/glusterd/src/glusterd-scrub-svc.c')
0 files changed, 0 insertions, 0 deletions