Bug 1683214 - [DOCS] OCS 3.11 upgrade: elaborate step regarding multiplexing
Summary: [DOCS] OCS 3.11 upgrade: elaborate step regarding multiplexing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 3.11.z Async
Assignee: Disha Walvekar
QA Contact: Aditya Ramteke
URL:
Whiteboard:
Depends On:
Blocks: 1845059
TreeView+ depends on / blocked
 
Reported: 2019-02-26 13:20 UTC by daniel
Modified: 2021-01-05 06:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-05 06:50:56 UTC
Embargoed:

Attachments (Terms of Use)

Description daniel 2019-02-26 13:20:14 UTC 
Document URL: 
-- app storage part 
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html/deployment_guide/chap-documentation-red_hat_gluster_storage_container_native_with_openshift_platform-upgrade#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Upgrade-Gluster_pods

-- registry-storage
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html/deployment_guide/chap-upgrade-glusterfs-registry-namespace#chap-registry-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Upgrade-Gluster_pods

Section Number and Name: 
app-storage:
6.1.3. Upgrading the Red Hat Gluster Storage Pods
    23. Brick multiplexing is a feature that allows adding multiple bricks into one process....

registry-storage:
6.2.3. Upgrading the Red Hat Gluster Storage Registry Pods
   22. Brick multiplexing is a feature that allows adding multiple bricks into one process....


Describe the issue: 
We just ask the customer to run # gluster volume set all cluster.brick-multiplex on  
which is, I think, not optimal as this is also a step when updating for 3.9 and requires volume to be stopped and started 

Suggestions for improvement: 
I think we should mention if it was previously updated from 3.9 this should have been already done and can be check with 
# gluster volume get  all cluster.max-bricks-per-process
and if already set there is no need to run that again (unless I am missing sth )


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