Bug 1359889
| Summary: | [RFE] ceph-ansible: journal_size should have default value for example 5G. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Vikhyat Umrao <vumrao> |
| Component: | ceph-ansible | Assignee: | seb |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
| Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | medium | ||
| Version: | 2 | CC: | adeza, aschoen, ceph-eng-bugs, flucifre, gmeno, jelopez, kdreyer, nthomas, sankarshan, seb |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | 3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
.The default value of `journal_size` is `0`
By default, the `journal_size` option in the `ceph-ansible` utility is set to `0`. This option is mandatory and Red Hat strongly recommends to reserve enough disk space for the journal, at least 5 GB depending on the size of your cluster. Using a journal smaller than 5 GB leads to critical performance issues and production stability problems.
For more details, see the https://access.redhat.com/documentation/en/red-hat-ceph-storage/2/single/configuration-guide#journal_settings[Journal Settings] section in the https://access.redhat.com/documentation/en/red-hat-ceph-storage/2/single/configuration-guide[Configuration Guide] for Red Hat Ceph Storage 2.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-12 13:57:35 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: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1322504 | ||
|
Description
Vikhyat Umrao
2016-07-25 16:02:22 UTC
PR opened here: https://github.com/ceph/ceph-ansible/pull/902 PR merged, in the process of pushing this downstream. This is not a blocker, let us document this var in the install guide. We can release it after 2.0 This is already documented in the install guide, so this one is more an enhancement requested by the consultants :) It's not really deployment issues but more production stability and performance issues. I'll also highlight critical performance problems that will occur with a journal_size < 5GB. LGTM thanks Bara! This will ship concurrently with RHCS 2.1. This looks like it is already in the stable-2.1 branch of ceph-ansible upstream. |