Project

General

Profile

Actions

Feature #16676

open

flush dirty data to journal on SIGTERM

Added by Douglas Fuller almost 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Correctness/Safety
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
MDS
Labels (FS):
Pull request ID:

Description

When it receives SIGTERM, the MDS should commit unsafe data to its journal before terminating.

Actions #1

Updated by Greg Farnum almost 8 years ago

  • Category set to Correctness/Safety
  • Component(FS) MDS added

We sort of assume that there's a standby and the client who will replay the op, but if we've lost the client it's (allowed to be) gone. And it's terribly inconvenient for testing certain things, as Doug discovered.

Actions #2

Updated by Greg Farnum almost 8 years ago

  • Tracker changed from Bug to Feature
Actions

Also available in: Atom PDF