Document URL:
I searched in this guide: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html-single/administration_guide/#Troubleshooting1
The above link is the only place I found how to restart a down brick process.
Section Number and Name:
None, as the requested data is missing
Describe the issue:
We need a troubleshooting or recover step that details how to start a brick that is no longer up and running.
The solution seems to be "gluster volume start <volname> force", but is not documented anywhere.
Suggestions for improvement:
As above
Additional information:
While we are at it, it may serve us to check and see what failure recovery steps for other such scenarios are covered in the documentation.
I keep on forgetting the credential for access.qa.redhat.com, so can't log into it till you pass back the user/password, Pratik.
In the mean time can you please paste the delta here?
Thanks Pratik for passing down the credential.
While the changes look mostly good, I think it'd be worth to mention (as a note) that in case of an OCS converged and independent mode where brick multiplexing is enabled by default, we'd need to force start all the volumes for which the bricks are multiplexed into a single process which went down. Makes sense?