Feature #20
closedclient: recover from a killed session (w/ blacklist)
0%
Description
The client_reconnect_stale config option no longer works because the blacklist/eviction logic changed significantly since it was introduced.
One option for a more robust solution is to create a new configuration option that allows the client to acquire a new cluster id (client.1234...), reconnect to the MDSs, and re-acquire all caps. In-flight ops should be retried. Cached reads and buffered writes should be dropped. Open file handles should return EIO.
Updated by Sage Weil almost 14 years ago
- Target version changed from v0.21 to v0.22
Updated by Sage Weil over 13 years ago
- Estimated time set to 10:00 h
- Source set to 5
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
485) - Translation missing: en.field_position set to 841
Updated by Sage Weil over 11 years ago
- Project changed from Ceph to CephFS
- Category deleted (
1)
Updated by Greg Farnum almost 8 years ago
- Category set to Administration/Usability
Updated by Patrick Donnelly over 5 years ago
- Subject changed from mds: allow client reconnect while up:active to client: recover from a killed session (w/ blacklist)
- Description updated (diff)
- Target version set to v14.0.0
- Start date deleted (
04/09/2010) - Source set to Development
- Component(FS) Client, kceph added
- Labels (FS) task(medium) added
I'm going to suggest attacking this problem from the other direction.
Updated by Patrick Donnelly about 5 years ago
- Target version changed from v14.0.0 to v15.0.0
Updated by Patrick Donnelly about 5 years ago
- Target version set to v15.0.0
- Estimated time deleted (
10:00 h)
Updated by Patrick Donnelly almost 5 years ago
- Status changed from New to Fix Under Review
- Assignee set to Zheng Yan
- Priority changed from Normal to High
- Backport set to nautilus
- Pull request ID set to 27435
Updated by Patrick Donnelly almost 5 years ago
- Copied to Feature #39967: kclient: recover from a killed session (w/ blacklist) added
Updated by Zheng Yan over 4 years ago
- Pull request ID changed from 27435 to 31480
Updated by Greg Farnum about 4 years ago
- Status changed from Fix Under Review to Resolved
Updated by Patrick Donnelly almost 4 years ago
- Target version changed from v15.0.0 to v16.0.0
this merged after octopus
Updated by Patrick Donnelly almost 4 years ago
- Related to Documentation #45573: doc: client: client_reconnect_stale=1 added
Updated by Nathan Cutler almost 4 years ago
- Status changed from Resolved to Pending Backport
- Backport set to octopus
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46402: octopus: client: recover from a killed session (w/ blacklist) added
Updated by Patrick Donnelly almost 4 years ago
Nathan, why was this changed to backport to Octopus?
Updated by Patrick Donnelly almost 4 years ago
Patrick Donnelly wrote:
Nathan, why was this changed to backport to Octopus?
I see: https://github.com/ceph/ceph/pull/35962#issuecomment-654945601
Updated by Nathan Cutler almost 4 years ago
Right. To summarize: the question whether it should be backported was asked, but got no answer, and in the meantime we are getting other backports that do not apply cleanly to octopus because this feature has not been backported.
But, that doesn't mean I insist on backporting it. It's just a proposal.
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Patrick Donnelly over 3 years ago
- Has duplicate Bug #42271: client: ceph-fuse which had been blacklisted couldn't auto reconnect after cluster unblacklisted it. added