Rados - improve ex-import functionality » History » Version 1
Jessica Mack, 07/03/2015 09:28 PM
1 | 1 | Jessica Mack | h1. Rados - improve ex-import functionality |
---|---|---|---|
2 | |||
3 | h3. Summary |
||
4 | |||
5 | There are several problems and missing functionality with 'rados export/import' tools. |
||
6 | |||
7 | h3. Owners |
||
8 | |||
9 | * Danny Al-Gaaf (Deutsche Telekom) |
||
10 | * Name (Affiliation) |
||
11 | * Name |
||
12 | |||
13 | h3. Interested Parties |
||
14 | |||
15 | * Marc Koderer ( Deutsche Telekom) |
||
16 | * Name (Affiliation) |
||
17 | * Name |
||
18 | |||
19 | h3. Current Status |
||
20 | |||
21 | h3. Detailed Description |
||
22 | |||
23 | The current implementation of 'rados export/import' has some issues: |
||
24 | * export/import speed is very slow |
||
25 | * export of large objects fails (e.g. big objects put via S3 into the cluster pool) due to limitation of extended attributes on the target filesystem |
||
26 | * depends on extended attributes support on local target filesystem |
||
27 | |||
28 | There are missing features: |
||
29 | * direct export from cluster1 and re-import in cluster2 in one run (could be faster and needed in some cases) |
||
30 | * verification, checksums |
||
31 | |||
32 | h3. Work items |
||
33 | |||
34 | h4. Coding tasks |
||
35 | |||
36 | * export performance: |
||
37 | ** random shuffle "ExportLocalFileWQ export_object_wq" before start export should increase the performance (dalgaaf: already implemented and tested, need to rebase and review) |
||
38 | * extended attributes: |
||
39 | ** use different approach than extended attributes or at least add option to export without |
||
40 | * direct export/import |
||
41 | ** add functions and options to export/import in one run |
||
42 | * verification/checksums |
||
43 | ** ... |
||
44 | |||
45 | h4. Build / release tasks |
||
46 | |||
47 | # Task 1 |
||
48 | # Task 2 |
||
49 | # Task 3 |
||
50 | |||
51 | h4. Documentation tasks |
||
52 | |||
53 | # Task 1 |
||
54 | # Task 2 |
||
55 | # Task 3 |
||
56 | |||
57 | h4. Deprecation tasks |
||
58 | |||
59 | # Support already exported pools to be imported again also with new implementation. |