| Summary: | [Async] Include a KS article link under erasure coding section | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Anjana Suparna Sriram <asriram> |
| Component: | doc-Administration_Guide | Assignee: | Laura Bailey <lbailey> |
| doc-Administration_Guide sub component: | 3.1 Release | QA Contact: | storage-qa-internal <storage-qa-internal> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | asriram, asrivast, lbailey, mpillai, nchilaka, rcyriac, rhinduja, rhs-bugs, storage-doc |
| Version: | rhgs-3.1 | Keywords: | ZStream |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.1.3 Async | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-26 13:00:15 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: | |
|
Description
Anjana Suparna Sriram
2016-11-24 09:43:49 UTC
As discussed earlier today, most of the information in the bug is already in the document as part of normal performance tuning. performance.client-io-threads is being added to the document as part of the RHGS 3.2 release, as it was unsupported for a time client.event-threads is documented in the tuning section of the Administration Guide, although it recommends 3 threads rather than 4 - is this change significant enough to add specifically to the dispersed, distributed-dispersed sections? Should we update to recommend 4 threads generally? Likewise, cluster.lookup-optimize is mentioned as a general recommendation for small file workloads, so nothing to change here. Alok, Anjana, what are your thoughts here? Hi Laura/Anjana, I don't see any changes or mention of the KS article under Erasure coding section. Point me the link if I missed out looks good to me. However the default of client.event-threads remains to be 2 but we are recommending user to set to 4 for better perf And as discussed on mail, there is no KS link being provided in the doc, but we are making sure all the options mentioned in the KS doc is available in the admin doc |