Project

General

Profile

Feature #14738

Optionally unregister "laggy" journal clients

Added by Jason Dillaman almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
02/11/2016
Due date:
% 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

Copied to rbd - Backport #17486: jewel: Optionally unregister "laggy" journal clients Resolved

History

#1 Updated by Mykola Golub over 2 years ago

  • Assignee set to Mykola Golub

#2 Updated by Mykola Golub over 2 years ago

  • Status changed from New to Need Review

#3 Updated by Mykola Golub over 2 years ago

  • Status changed from Need Review to Resolved

#4 Updated by Jason Dillaman over 2 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to jewel

#5 Updated by Loic Dachary over 2 years ago

  • Copied to Backport #17486: jewel: Optionally unregister "laggy" journal clients added

#6 Updated by Loic Dachary over 2 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF