diff options
| author | Loic Dachary <loic@dachary.org> | 2013-08-05 15:07:36 +0200 |
|---|---|---|
| committer | Loic Dachary <loic@dachary.org> | 2013-08-05 15:09:55 +0200 |
| commit | 128628824bb1b132395fa74a12aeca2a0313390f (patch) | |
| tree | 9fa96d8bfbb915c4edf0966ab1726809ae7f5634 | |
| parent | 160fa710ecbf026e4ebbbc71a6fca35e59107eb7 (diff) | |
| download | ceph-128628824bb1b132395fa74a12aeca2a0313390f.tar.gz | |
Add links to backfill related tracker items.
Signed-off-by: Loic Dachary <loic@dachary.org>
| -rw-r--r-- | doc/dev/osd_internals/erasure_coding.rst | 15 |
1 files changed, 9 insertions, 6 deletions
diff --git a/doc/dev/osd_internals/erasure_coding.rst b/doc/dev/osd_internals/erasure_coding.rst index f9c34671569..f81453d6825 100644 --- a/doc/dev/osd_internals/erasure_coding.rst +++ b/doc/dev/osd_internals/erasure_coding.rst @@ -278,7 +278,7 @@ PGBackend interfaces: - recoverable() - recover_object() -Backfill +`Backfill <http://tracker.ceph.com/issues/5856>`_ -------- For the most part, backfill itself should behave similarly between @@ -292,14 +292,17 @@ replicated and erasure coded pools with a few exceptions: temporary pg chunk for that acting set slot. For 2, we don't really need to place the backfill peer in the acting -set for replicated PGs anyway. For 1, PGBackend::choose_backfill() -should determine which osds are backfilled in a particular interval. +set for replicated PGs anyway. +For 1, PGBackend::choose_backfill() should determine which osds are +backfilled in a particular interval. Core changes: -- Backfill should be capable of handling multiple backfill peers - concurrently even for replicated pgs (easier to test for now) -- Backfill peers should not be placed in the acting set. +- Backfill should be capable of `handling multiple backfill peers + concurrently <http://tracker.ceph.com/issues/5858>`_ even for + replicated pgs (easier to test for now) +- `Backfill peers should not be placed in the acting set + <http://tracker.ceph.com/issues/5855>`_. PGBackend interfaces: |