Bug 1319326 - RFE Set Ceph osd journal size to 5GB in OSP-d
Summary: RFE Set Ceph osd journal size to 5GB in OSP-d
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ga
: 10.0 (Newton)
Assignee: Jiri Stransky
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 21:00 UTC by Alexandre Marangone
Modified: 2016-08-09 12:13 UTC (History)
15 users (show)

Fixed In Version: openstack-tripleo-heat-templates-5.0.0-0.20160725225924.77f6c40.el7ost
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-02 11:37:03 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1589909 0 None None None 2016-06-07 10:25:49 UTC
OpenStack gerrit 323245 0 None None None 2016-05-31 09:59:31 UTC

Description Alexandre Marangone 2016-03-18 21:00:18 UTC
Description of problem:
osd_journal_size is currently set to 1GB in OSP-d while Ceph's default is 5GB. This RFE is to align OSP-d's osd_journal_size value to Ceph's default.

source: https://github.com/ceph/ceph/blob/hammer/src/common/config_opts.h#L492

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

Comment 2 Mike Burns 2016-04-07 21:14:44 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 3 Erno Kuvaja 2016-05-11 11:35:16 UTC
Hi Angus,

I could try to drive this change via upstream getting TripleO providing sensible defaults to the deployment. If you are ok with that feel free to assign the bug to me and I'll start working on it.

Comment 5 Emilien Macchi 2016-05-12 17:21:16 UTC
Regarding the upgrade thing, if we change the default value, we need to orchestrate the upgrade in THT upgrade scripts, so increase the journal size before puppet runs, so when puppet runs, journal size is already good.

Can we have Ceph experts on this task? Can we scale-up the journal size without downtime?

Thanks

Comment 6 Erno Kuvaja 2016-05-18 10:33:03 UTC
After reading into ceph documentation[1] I'm not convinced that we should change the default. I do not know where that 5GB default is from that is mentioned in the bug description but current default for journal size is 0 and there is clear note that the required journal size is based on the deployment characteristics and should be calculated based on those.

the current 1GB might be something that works in our CI well and every single deployment should overwrite this based on the 'osd journal size = {2 * (expected throughput * filestore max sync interval)}' calculation.

Perhaps there would be rather documentation change in place than changing the default value on the deployment scripts that should be overwritten anyways at the runtime?

[1] http://docs.ceph.com/docs/master/rados/configuration/osd-config-ref/#journal-settings

Comment 7 Erno Kuvaja 2016-05-18 10:54:00 UTC
Ah just realized where that was coming from. Interestingly the hammer config reference section is exactly the same claiming the default being 0
http://docs.ceph.com/docs/hammer/rados/configuration/osd-config-ref/#journal-settings

Comment 8 Alexandre Marangone 2016-05-18 15:54:59 UTC
That's likely a documentation error. It's been to 5GB for a while now (https://github.com/ceph/ceph/blob/hammer/src/common/config_opts.h#L495)

Things may have changed a bit since the last time I looked into it but my understanding of this variable is that it will only be used to create a journal partition of osd_journal_size MB when running ceph-disk prepare and used when creating the Ceph journal (ceph-osd -i <ID> --mkjournal).
Changing this value won't matter for existing OSDs.

Comment 9 Erno Kuvaja 2016-05-25 13:37:06 UTC
Thanks Alexander,

So if I understand correctly this should be really straight forward change to make not affecting the upgrades.

Comment 10 Erno Kuvaja 2016-05-31 09:59:31 UTC
I've proposed change to the upstream to remove the overwrite of osd_journal_size. As that option affects only during the journal creation and ceph does have sensible default lets just stay on that and if ceph developers sees reason to change the default we get that benefit as well without changing the overwrite again.

Comment 11 Erno Kuvaja 2016-06-07 10:25:50 UTC
The change merged into master. Bug opened for backporting into mitaka.

Comment 12 RHEL Program Management 2016-08-02 11:37:03 UTC
Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

Comment 13 Jeff Brown 2016-08-05 15:47:45 UTC
Adding to clarify, as comment 12 has continually confused me.

This is already fixed in OSP9, therefore it is closed in the context of OSP10 and the desired functionality is present.


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