Bug 1218567 - Upcall: Cleanup the expired upcall entries
Summary: Upcall: Cleanup the expired upcall entries
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: upcall
Version: 3.7.0
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Soumya Koduri
QA Contact:
URL:
Whiteboard: FutureFeature
Depends On: 1200267
Blocks: glusterfs-3.7.0 1200262 1217711
TreeView+ depends on / blocked
 
Reported: 2015-05-05 09:24 UTC by Soumya Koduri
Modified: 2015-05-15 17:09 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.7.0
Doc Type: Bug Fix
Doc Text:
Clone Of: 1200267
Environment:
Last Closed: 2015-05-15 17:09:50 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Soumya Koduri 2015-05-05 09:24:23 UTC
+++ This bug was initially created as a clone of Bug #1200267 +++

Description of problem:

Need support to cleanup all the expired/stale upcall client entries maintained by the upcall xlator.

--- Additional comment from Soumya Koduri on 2015-03-12 01:39:20 EDT ---

Also note that "inode_forget" is never called on non-exmpty directories. This is to take that into account while trying to cleanup the entries.

--- Additional comment from Soumya Koduri on 2015-03-16 09:20:45 EDT ---

In addition - will address below comments received as part of
http://review.gluster.org/#/c/9535 - 

* Instead of client_uid, use client_ref(client) in upcall_client_entry structure. But that may result in not cleaning up client object incase of network disconnects.

--- Additional comment from Anand Avati on 2015-04-22 14:31:44 EDT ---

REVIEW: http://review.gluster.org/10342 (Upcall: Cleanup expired client entries) posted (#1) for review on master by soumya k (skoduri)

--- Additional comment from Anand Avati on 2015-04-23 10:13:01 EDT ---

REVIEW: http://review.gluster.org/10342 (Upcall: Cleanup expired client entries) posted (#2) for review on master by soumya k (skoduri)

--- Additional comment from Anand Avati on 2015-04-24 13:24:40 EDT ---

REVIEW: http://review.gluster.org/10342 (Upcall: Cleanup expired client entries) posted (#3) for review on master by soumya k (skoduri)

--- Additional comment from Anand Avati on 2015-04-27 05:06:59 EDT ---

REVIEW: http://review.gluster.org/10342 (Upcall: Cleanup expired client entries) posted (#4) for review on master by soumya k (skoduri)

Comment 1 Anand Avati 2015-05-05 09:54:51 UTC
REVIEW: http://review.gluster.org/10566 (Upcall: Cleanup expired client entries) posted (#1) for review on release-3.7 by soumya k (skoduri)

Comment 2 Anand Avati 2015-05-06 10:02:02 UTC
REVIEW: http://review.gluster.org/10566 (Upcall: Cleanup expired client entries) posted (#3) for review on release-3.7 by soumya k (skoduri)

Comment 3 Niels de Vos 2015-05-15 17:09:50 UTC
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


Note You need to log in before you can comment on or make changes to this bug.