Description of problem: When "gluster volume get" is executed on a volume with default options, the value of "server.tcp-user-timeout" is reported as "0", but its real default value is "42". Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. gluster volume create test host:/brick 2. gluster volume get test server.tcp-user-timeout 3. Actual results: The value shown is "0" Expected results: It should show "42" Additional info: This happens because glusterd doesn't look for default values for options at the same places that xlators are actually using when running.
REVIEW: https://review.gluster.org/21709 (core: create a constant for default network timeout) posted (#1) for review on master by Xavi Hernandez
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/