Bug 1375389 - [Doc] Wrongly mentioned primary OSD number in storage strategies guide
Summary: [Doc] Wrongly mentioned primary OSD number in storage strategies guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Documentation
Version: 2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 2.1
Assignee: Bara Ancincova
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 01:04 UTC by Prashant Dhange
Modified: 2016-09-30 17:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-30 17:21:18 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Prashant Dhange 2016-09-13 01:04:02 UTC
Description of problem:
Document Red_Hat_Ceph_Storage-2-Storage_Strategies_Guide-en-US, Chapter 3 - Section  3.1. ABOUT PLACEMENT GROUPS
https://access.redhat.com/documentation/en/red-hat-ceph-storage/2/paged/storage-strategies-guide/chapter-3-placement-groups-pgs

The below section has minor mistake with primary OSD 1 is being documented instead of primary OSD 5.

For example, if CRUSH assigns an object to a placement group, and the placement group is assigned to OSD 5 as the primary OSD, if CRUSH calculates that OSD 1 and OSD 8 are secondary OSDs for the placement group, the primary OSD 1 will copy the data to OSDs 1 and 8. By copying data on behalf of clients, Ceph simplifies the client interface and reduces the client workload.

Version-Release number of selected component (if applicable):
Ceph 2.0

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
For example, if CRUSH assigns an object to a placement group, and the placement group is assigned to OSD 5 as the primary OSD, if CRUSH calculates that OSD 1 and OSD 8 are secondary OSDs for the placement group, the primary OSD 1 will copy the data to OSDs 1 and 8. By copying data on behalf of clients, Ceph simplifies the client interface and reduces the client workload.

Expected results:
For example, if CRUSH assigns an object to a placement group, and the placement group is assigned to OSD 5 as the primary OSD, if CRUSH calculates that OSD 1 and OSD 8 are secondary OSDs for the placement group, the primary OSD 5 will copy the data to OSDs 1 and 8. By copying data on behalf of clients, Ceph simplifies the client interface and reduces the client workload.

Additional info:

Comment 3 Prashant Dhange 2016-09-13 01:10:41 UTC
There is another minor mistake in section 3.1, "will" repeated twice:

Should the primary OSD fail and get marked out of the cluster, CRUSH will assign the placement group to another OSD, which will will receive copies of objects in the placement group. Another OSD in the Up Set will assume the role of the primary OSD.

Expected:
Should the primary OSD fail and get marked out of the cluster, CRUSH will assign the placement group to another OSD, which will receive copies of objects in the placement group. Another OSD in the Up Set will assume the role of the primary OSD.


Note You need to log in before you can comment on or make changes to this bug.