Project

General

Profile

Actions
Copy link

Feature #14738

closed

Optionally unregister "laggy" journal clients

Added by Jason Dillaman about 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Mykola Golub
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Reviewed:
Affected Versions:
Pull request ID:

Description

Support an optional configuration setting for the maximum number of object sets a journal client can be behind before it is automatically unregistered. This will protect the journal from growing to an infinite size.

Related issues 1 (0 open — 1 closed)

Copied to rbd - Backport #17486: jewel: Optionally unregister "laggy" journal clientsResolvedJason DillamanActions
Actions
Copy link
 #1

Updated by Mykola Golub almost 8 years ago

  • Assignee set to Mykola Golub
Actions
Copy link
 #2

Updated by Mykola Golub almost 8 years ago

  • Status changed from New to Fix Under Review
Actions
Copy link
 #3

Updated by Mykola Golub over 7 years ago

  • Status changed from Fix Under Review to Resolved
Actions
Copy link
 #4

Updated by Jason Dillaman over 7 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to jewel
Actions
Copy link
 #5

Updated by Loïc Dachary over 7 years ago

  • Copied to Backport #17486: jewel: Optionally unregister "laggy" journal clients added
Actions
Copy link
 #6

Updated by Loïc Dachary over 7 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF