Project

General

Profile

Actions

Feature #2477

closed

rados bench cleanup

Added by Greg Farnum almost 12 years ago. Updated over 11 years ago.

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

0%

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

Description

Right now rados bench write leaves a lot of data just lying around the cluster, without a good way to clean itself up.

  • by default, clean up after each run
  • optionally, do not clean up
  • advertise our object prefix loudly on startup
  • make the prefix always share some unique-ish prefix (before the unique-to-this-run-goo)
  • allow cleanup of earlier runs by specifying the prefix, or all runs by specifying the generic prefix
Actions #1

Updated by Sage Weil almost 12 years ago

  • Translation missing: en.field_position set to 5
Actions #2

Updated by Sage Weil almost 12 years ago

  • Status changed from New to 12

I think we need both:

  • clean up objects after each run
  • search+clean up objects from previous (maybe aborted) runs

Whether that is a search (blah) or a well-known object where we register runs before they start and deregister after cleanup is an open question...

Actions #3

Updated by Sage Weil almost 12 years ago

  • Translation missing: en.field_position deleted (17)
  • Translation missing: en.field_position set to 14
Actions #4

Updated by Sage Weil almost 12 years ago

  • Target version set to v0.49
  • Translation missing: en.field_position deleted (38)
  • Translation missing: en.field_position set to 1
  • Translation missing: en.field_position changed from 1 to 1299
Actions #5

Updated by Sage Weil almost 12 years ago

  • Subject changed from rados bench should offer an option to clean up data to rados bench cleanup
  • Translation missing: en.field_position deleted (1304)
  • Translation missing: en.field_position set to 1304
Actions #6

Updated by Sage Weil almost 12 years ago

  • Translation missing: en.field_story_points set to 3
  • Translation missing: en.field_position deleted (1300)
  • Translation missing: en.field_position set to 1300
Actions #7

Updated by Sage Weil almost 12 years ago

  • Translation missing: en.field_story_points deleted (3)
  • Translation missing: en.field_position deleted (1300)
  • Translation missing: en.field_position set to 1300
Actions #8

Updated by Sage Weil almost 12 years ago

  • Description updated (diff)
Actions #9

Updated by Sage Weil almost 12 years ago

  • Translation missing: en.field_story_points set to 5
  • Translation missing: en.field_position deleted (1303)
  • Translation missing: en.field_position set to 78
Actions #10

Updated by Sage Weil almost 12 years ago

  • Translation missing: en.field_position deleted (78)
  • Translation missing: en.field_position set to 1309
Actions #11

Updated by Sage Weil almost 12 years ago

  • Translation missing: en.field_position deleted (1309)
  • Translation missing: en.field_position set to 1311
Actions #12

Updated by Sage Weil almost 12 years ago

  • Target version deleted (v0.49)
  • Translation missing: en.field_position deleted (1311)
  • Translation missing: en.field_position set to 1
Actions #13

Updated by Sage Weil over 11 years ago

  • Target version set to v0.51
  • Translation missing: en.field_position deleted (30)
  • Translation missing: en.field_position set to 8
Actions #14

Updated by Sage Weil over 11 years ago

  • Status changed from 12 to Fix Under Review
Actions #15

Updated by Sage Weil over 11 years ago

  • Assignee set to Anonymous
Actions #16

Updated by Sage Weil over 11 years ago

  • Target version changed from v0.51 to 83
  • Translation missing: en.field_position deleted (47)
  • Translation missing: en.field_position set to 3
Actions #17

Updated by Sage Weil over 11 years ago

  • Status changed from Fix Under Review to Resolved
Actions #18

Updated by Sage Weil over 11 years ago

  • Target version changed from 83 to v0.52a
Actions

Also available in: Atom PDF