Project

General

Profile

Feature #3891

osd: move purged_snaps out of info

Added by Sage Weil about 11 years ago. Updated about 11 years ago.

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

0%

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

History

#1 Updated by Sage Weil about 11 years ago

  • Target version set to v0.57c
  • translation missing: en.field_position deleted (2)
  • translation missing: en.field_position set to 6

#2 Updated by Ian Colle about 11 years ago

  • Assignee set to David Zafman

#3 Updated by Ian Colle about 11 years ago

  • Status changed from New to In Progress

#4 Updated by Ian Colle about 11 years ago

  • translation missing: en.field_position deleted (9)
  • translation missing: en.field_position set to 8

#5 Updated by Ian Colle about 11 years ago

  • Target version changed from v0.57c to v0.58
  • translation missing: en.field_position deleted (8)
  • translation missing: en.field_position set to 2

#6 Updated by David Zafman about 11 years ago

  • Status changed from In Progress to Fix Under Review

#7 Updated by David Zafman about 11 years ago

  • Status changed from Fix Under Review to Resolved

#8 Updated by David Zafman about 11 years ago

commit 188f3ea6867eeb6e950f6efed18d53ff17522bbc
Author: David Zafman <>
Date: Mon Feb 11 12:20:23 2013 -0800

osd/PG: store pg_info_t in leveldb (omap), purged_snaps separately
Separate the purged_snaps portion of pg_info_t (the one that gets big).
Feature #3891: osd: move purged_snaps out of info
Add a separate dirty_big_info flag so that we only update the pginfo
"biginfo" file if that state changes. This lets us avoid the cost in the
general case, like a regular PG write.
Add LEVELDBINFO feature
Put info, biginfo in leveldb
Move epoch to omap
Feature #3892: osd: move pg info into leveldb
Signed-off-by: Sage Weil &lt;&gt;
Signed-off-by: David Zafman &lt;&gt;
Reviewed-by: Sage Weil &lt;&gt;
Reviewed-by: Sam Just &lt;&gt;

Also available in: Atom PDF