Covers 1-node cluster issues, fewer OSDs than replicas, and
active + clean + inconsistent states in greater detail.
Signed-off-by: John Wilkins <john.wilkins@inktank.com>
Latest version of librados uses write_full when writing entire object.
Should the documentation mention that the method "write" used to serve
this function.
Signed-off-by: Kevin Dalley <kevin@kelphead.org>
And a link from rados/operations.
http://tracker.ceph.com/issues/8514Fixes: #8514
Reported-by: Kenneth Waegeman <Kenneth.Waegeman@UGent.be>
Signed-off-by: Loic Dachary <loic@dachary.org>
The properties are replaced with erasure code profiles. Remove the
reference to properties and the documentation of each erasure-code
related property.
Signed-off-by: Loic Dachary <loic@dachary.org>
The instructions for 'osd tier add' were plain
wrong, claiming that the cache mode could
be passed as a third argument.
Signed-off-by: John Spray <john.spray@inktank.com>
The pid file behavior changed over time and the description is misleading.
http://tracker.ceph.com/issues/8324Fixes: #8324
Signed-off-by: Loic Dachary <loic@dachary.org>
wip-mon-docs: Better explain required number of monitors & how to troubleshoot a monitor
Signed-off-by: Joao Eduardo Luis <joao.luis@inktank.com>
Reviewed-by: Loic Dachary <loic@dachary.org>
Previous commit (047287afbe0ddfaaafd05e9dbf25c1c7dea9a1be) broke
formatting on the formula, and also made mixed formula and text oddly,
which on second thought didn't look too good.
Add the note about the power of two to the following paragraph
instead, in prose.
Signed-off-by: Florian Haas <florian@hastexo.com>
Following an IRC discussion, it emerged that it would be helpful
to explain the merit of choosing a number of PGs per pool that is
a power of two, to keep PGs at roughly equal sizes in case of
PG splits.
See http://irclogs.ceph.widodh.nl/index.php?date=2014-03-12 for the
original discussion.
Signed-off-by: Florian Haas <florian@hastexo.com>
Include erasure code information. A choice is made to display properties
that should be documented as part of the erasure code plugin
interface (erasure-code-k for instance). However, there only is one
plugin at the moment. Furthermore, erasure-code-k and erasure-code-m are
the two properties that the system administrator will want to tweak when
playing with erasure coded pools for the first time. It is probably
better to document them in a very visible place for this reason.
http://tracker.ceph.com/issues/7548 refs #7548
Signed-off-by: Loic Dachary <loic@dachary.org>
