Project

General

Profile

Actions
Copy link

Feature #3527

closed

osd: blacklist should cancel outstanding watches from blacklisted client

Added by Dan Mick over 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
David Zafman
Category:
-
Target version:
v0.65
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

While testing locking/fencing, I noticed that if an rbd client is blacklisted, it
receives ESHUTDOWN from any operation following; this unfortunately includes the
"remove watch" operation, which means that it exits with pending watches, which means
the image it was doing I/O to cannot be removed until the 30s timeout expires.

Blacklist should probably immediately expire and/or cancel outstanding watches from
the client being blacklisted.

Actions
Copy link
 #1

Updated by Sage Weil about 11 years ago

  • Tracker changed from Bug to Feature
Actions
Copy link
 #2

Updated by Sage Weil almost 11 years ago

  • Subject changed from blacklist should cancel outstanding watches from blacklisted client to osd: blacklist should cancel outstanding watches from blacklisted client
Actions
Copy link
 #3

Updated by Sage Weil almost 11 years ago

  • Translation missing: en.field_story_points set to 5.00
Actions
Copy link
 #4

Updated by Sage Weil almost 11 years ago

  • Target version set to v0.63
Actions
Copy link
 #5

Updated by Sage Weil almost 11 years ago

  • Target version changed from v0.63 to v0.64
Actions
Copy link
 #6

Updated by Ian Colle almost 11 years ago

  • Assignee set to David Zafman
Actions
Copy link
 #7

Updated by Ian Colle almost 11 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #8

Updated by Sage Weil almost 11 years ago

  • Target version changed from v0.64 to v0.65
Actions
Copy link
 #9

Updated by David Zafman almost 11 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF