Description of problem: The following volume set options doesn't have default value and description in the volume set help 1.features.lock-heal 2.features.grace-timeout 3.cluster.server-quorum-type 4.cluster.server-quorum-ratio Version-Release number of selected component (if applicable):RHS-2.0.u3 How reproducible:Always Steps to Reproduce: 1.Run gluster volume set help command 2.Look for the above mentioned options 3. Actual results: For some options , there are no default value and description. Expected results: For all the options there should be default value and description. Additional info:
Can we check them all? # gluster volume set test2 network.ping-timeout 40 Set volume successful # gluster volume set help| grep ping # gluster volume set help| grep net #
Still few of the options have default value set to (null), if it is not set to anything, mention it is not set to any value. And about the description, it is not clear on what a particular option can be used for. eg: Option: features.grace-timeout Default Value: (null) Description: Sets the grace-timeout value. Valid range 10-1800. without checking the description I would know it set grace-timeout value, but it doesn't say where and how I can use it . Good example of description for an option, Option: cluster.data-self-heal-algorithm Default Value: (null) Description: Select between "full", "diff". The "full" algorithm copies the entire file from source to sink. The "diff" algorithm copies to sink only those blocks whose checksums don't match with those of source. If no option is configure d the option is chosen dynamically as follows: If the file does not exist on one of the sinks or empty file exists or if the source file size is about the same as page size the entire file will be read and written i.e "full" algo, otherwise "diff" algo is chosen.
adding 3.0 flag and removing 2.1.z
The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version. [1] https://rhn.redhat.com/errata/RHSA-2014-0821.html