Bug 1593868

Summary: Best practices updates for bucket index to be on same nvme as journal
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasu Kulkarni <vakulkar>
Component: DocumentationAssignee: John Wilkins <jowilkin>
Status: CLOSED CURRENTRELEASE QA Contact: Vasu Kulkarni <vakulkar>
Severity: high Docs Contact:
Priority: high    
Version: 3.1CC: agunn, asriram, dfuller, hnallurv, jharriga, kdreyer, pasik, seb
Target Milestone: rc   
Target Release: 3.1   
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: 2019-02-26 07:25:14 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: 1581350, 1591074, 1593418, 1602919    

Description Vasu Kulkarni 2018-06-21 17:43:13 UTC
Description of problem:

The current GSS best practices guide recommends bucket index to be on separate nvm drive compared to journal,

During the DFG workload testing, John noticed too much traffic is on the filestore journals and there is not really advantageous to have bucket index on different nvme, the recommendation from the experiment is to split on same nvme probably using lvm, we need to update our best practices guide based on this testing.

Comment 3 Vasu Kulkarni 2018-06-27 17:47:02 UTC
So what John is recommending here is with LVM option that is equally split between journal and bucket index on same nvme.

Comment 5 Vasu Kulkarni 2018-09-04 17:28:26 UTC
One minor nit but looks good.