Project

General

Profile

Actions

Feature #9262

closed

Additional namespace issues

Added by David Zafman over 9 years ago. Updated over 9 years ago.

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

0%

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

Description

I’ve identified the following namespace issues:

1. "rados cppool" only copies objects in default namespace
2. "rados cp" and “rados clonedata” commands have no way to specify the target’s namespace
3. “rados cache-flush-evict-all” and “rados cache-try-flush-evict-all” only evicts objects in the default namespace

These can easily be fixed in conjunction with or after feature # 9031.


Related issues 3 (0 open3 closed)

Related to Ceph - Feature #9403: Make rados import/export fully functional and re-enableDuplicateDavid Zafman09/09/2014

Actions
Has duplicate Ceph - Feature #1091: librados: support pgls filterDuplicate05/16/2011

Actions
Blocked by Ceph - Feature #9031: List RADOS namespaces and list all objects in all namespacesResolvedDavid Zafman08/06/2014

Actions
Actions #1

Updated by David Zafman over 9 years ago

Support for rados export/import:

Given a directory export will do the following:

All default namespace objects will be stored in the top-level directory as before. Each namespace will create a sub-directory with the name of the namespace and store the those namespace objects in the sub-directory.

Import use the export directory structure to create all the objects in the appropriate namespaces.

Actions #2

Updated by David Zafman over 9 years ago

For now we will disable rados export/import (see feature #9403 to re-enable).

Actions #3

Updated by David Zafman over 9 years ago

  • Status changed from New to Fix Under Review
Actions #4

Updated by David Zafman over 9 years ago

  • Status changed from Fix Under Review to 7
Actions #5

Updated by Samuel Just over 9 years ago

  • Status changed from 7 to Resolved
Actions

Also available in: Atom PDF