Bug 1368827

Summary: optimizing the gluster volume from UI should set the network.ping-timeout value to 30 seconds
Product: [oVirt] ovirt-engine Reporter: SATHEESARAN <sasundar>
Component: Frontend.WebAdminAssignee: Sahina Bose <sabose>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.2.7CC: bugs, mmalhotr, sabose, sasundar
Target Milestone: ovirt-4.1.0-betaFlags: rule-engine: ovirt-4.1+
rule-engine: planning_ack+
sabose: devel_ack+
sasundar: testing_ack+
Target Release: 4.1.0.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-15 14:49:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1277939    

Description SATHEESARAN 2016-08-21 17:24:28 UTC 
Description of problem:
-----------------------
Optimizing the gluster volume for virt store from RHV UI, set the network.ping-timeout value to 10 seconds. This value is too less, so that with more VMs, one may see hearbeat exceeded problems. The recommended value for network.ping-timeout is 30 seconds


Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHV 4.0.2-7


How reproducible:
------------------
Always

Steps to Reproduce:
-------------------
1. Create a gluster replica 3 volume
2. Optimize the volume for virt-store by clicking 'Optimize for virt-store' tab under the 'volumes' tab


Actual results:
---------------
network.ping-timeout value is set to 10 seconds

Expected results:
------------------
network.ping-timeout value should be set to 30 seconds
Comment 1 SATHEESARAN 2016-08-21 17:25:51 UTC 
After optimizing the volume for virt-store from RHV UI, the volume options looks as follows :

[root@ ~]# gluster volume info
 
Volume Name: rep3vol
Type: Replicate
Volume ID: 6ca6c874-350f-488b-aae0-ca0aae11bc2f
Status: Created
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: node1.redhat.com:/rhgs/brick1/brick1
Brick2: node2.redhat.com:/rhgs/brick1/brick1
Brick3: node3.redhat.com:/rhgs/brick1/brick1
Options Reconfigured:
network.ping-timeout: 10
server.allow-insecure: on
storage.owner-gid: 36
storage.owner-uid: 36
cluster.server-quorum-type: server
cluster.quorum-type: auto
network.remote-dio: enable
cluster.eager-lock: enable
performance.stat-prefetch: off
performance.io-cache: off
performance.read-ahead: off
performance.quick-read: off
auth.allow: *
user.cifs: disable
nfs.disable: on
performance.readdir-ahead: on
Comment 3 Sahina Bose 2016-12-16 06:07:47 UTC 
Is the network.ping-timeout set to 30 seconds in group virt of gluster?
Comment 4 SATHEESARAN 2016-12-20 07:46:49 UTC 
(In reply to Sahina Bose from comment #3)
> Is the network.ping-timeout set to 30 seconds in group virt of gluster?

Sahina,

No. Its not the part of the group virt.

I think the value of ping-timeout=10secs is burned (hard-coded) somewhere in the vdsm code
Comment 5 SATHEESARAN 2017-02-08 17:51:58 UTC 
Tested with RHV 4.1 beta1 ( Red Hat Virtualization Manager Version: 4.1.0.3-0.1.el7 )

When the volume optimized for virt-store, the volume option 'network.ping-timeout' was set to 30 seconds now