Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1359889 - [RFE] ceph-ansible: journal_size should have default value for example 5G.
[RFE] ceph-ansible: journal_size should have default value for example 5G.
Status: CLOSED CURRENTRELEASE
Product: Red Hat Storage Console
Classification: Red Hat
Component: ceph-ansible (Show other bugs)
2
x86_64 Linux
medium Severity medium
: ---
: 3
Assigned To: seb
ceph-qe-bugs
Bara Ancincova
: FutureFeature
Depends On:
Blocks: 1322504
  Show dependency treegraph
 
Reported: 2016-07-25 12:02 EDT by Vikhyat Umrao
Modified: 2017-04-12 09:57 EDT (History)
10 users (show)

See Also:
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 09:57:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vikhyat Umrao 2016-07-25 12:02:22 EDT
Description of problem:
[RFE] ceph-ansible: journal_size should have default value for example 5G.


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

We had some issues with customers. Where customer choose Journal size as 1024M and it created lot of issues for their deployment.

As they had approx 300+ OSDs it was hard to reconfigure journal and it was like we need to redeploy the cluster. 

I have attached the customer case# 01518937 with this bug.
Comment 2 seb 2016-07-25 12:18:35 EDT
PR opened here: https://github.com/ceph/ceph-ansible/pull/902
Comment 3 seb 2016-07-26 08:51:16 EDT
PR merged, in the process of pushing this downstream.
Comment 7 Gregory Meno 2016-07-26 18:08:10 EDT
This is not a blocker, let us document this var in the install guide. We can release it after 2.0
Comment 9 seb 2016-07-27 07:59:27 EDT
This is already documented in the install guide, so this one is more an enhancement requested by the consultants :)
Comment 11 seb 2016-08-11 10:55:28 EDT
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.
Comment 13 seb 2016-08-12 05:27:19 EDT
LGTM thanks Bara!
Comment 15 Federico Lucifredi 2016-10-07 12:59:49 EDT
This will ship concurrently with RHCS 2.1.
Comment 16 Andrew Schoen 2017-03-03 11:05:08 EST
This looks like it is already in the stable-2.1 branch of ceph-ansible upstream.

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