| Summary: | [Doc RFE] Add a new section on how to support 3-way sharded-replicated volumes | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Anjana Suparna Sriram <asriram> |
| Component: | doc-Administration_Guide | Assignee: | Laura Bailey <lbailey> |
| doc-Administration_Guide sub component: | Default | QA Contact: | RamaKasturi <knarra> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | asriram, asrivast, avishwan, kdhananj, lbailey, mhideo, nlevinki, rcyriac, rhinduja, rhs-bugs, rwheeler, sasundar, storage-doc |
| Version: | rhgs-3.1 | Keywords: | Documentation, FutureFeature, ZStream |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.1.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-29 14:19:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1319579 | ||
| Bug Blocks: | 1311845 | ||
|
Description
Anjana Suparna Sriram
2016-03-15 11:13:14 UTC
Looks good. Geo-rep Changes looks good. one minor comment about example heading(comment from Kotresh) "Example: Three-way geo-replicated sharded volumes" Three way geo-replicated is confusing, can be changed to Example: geo-replicated sharded volumes Hi Laura, I looked at the documentation and have some comments. sharding is an use case only supported to provide storage for live virtual machine images. 1) Following lines have to be put under "Important" banner, "As of Red Hat Gluster Storage 3.1 Update 3, sharding has one supported use case: in the context of providing Red Hat Gluster Storage as a storage domain for Red Hat Enterprise Virtualization, to provide storage for live virtual machine images" under 16.1 section. 2) This has to be removed from the guide as we are not supporting add/ remove bricks in this particular use case as the deployment as of now supported is only 1 * 3 volume. "Sharding also lets you increase volume capacity by adding bricks to a volume in an ad-hoc fashion. This is much more convenient than techniques like striping, which require bricks to be added in multiples of replica and stripe count. " 3) I am not sure why do we have the sections 16.1.1 and 16.1.2. A volume which is sharded can be geo-replicated and if we have any extra options for performing geo-replication on a sharded volume i think we need to document those. AFAIK,allows more efficient synchronization because only the file pieces that change need to be synchronized. 4) One important thing is sharding is supported only for net new deployments and only supported to provide storage for live VM images. I think we can remove the section 16.2 from the guide. 5) Supported value for shard block size for vm use case is 512MB. Can you please remove the value 4MB–4TB and say supported and is only 521MB. In Comment 13 i put the supported value as 521MB, please s/521MB/512MB. @ Alok, can you please review my comments in comment 13 and let me know if i am missing something ? sas, could you also please review my comments ? verified in the link provided in comment 23 and looks good . |