Bug 1683529

Summary: glusterfs slice setup is missing in gluster-ansible-roles
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Sachidananda Urs <surs>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.6CC: godas, pasik, rhs-bugs, sabose, sankarshan, sasundar, surs
Target Milestone: ---   
Target Release: RHHI-V 1.6   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, Red Hat Hyperconverged Infrastructure for Virtualization did not configure a system slice to limit the resource usage allowed to Red Hat Gluster Storage. This meant that when storage was under high load, it consumed too many system resources. Storage processes are now configured to use up to one third of system resources.
Story Points: ---
Clone Of: 1683528 Environment:
Last Closed: 2019-05-09 06:09:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1683528    
Bug Blocks: 1672932    

Description SATHEESARAN 2019-02-27 06:51:04 UTC
Description of problem:
-----------------------
As there are gluster and virt services are running on the same host/machines,
gluster slice setup is required to cap the number of cores consumed by gluster process. Gdeploy has gone with the standard value of 33% cores allocated to gluster process. The same needs to implemented with gluster-ansible roles too.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-ansible-roles-1.0.4-3

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

Steps to Reproduce:
-------------------
1. Complete RHHI-V deployment with RHVH 4.3

Actual results:
---------------
gluster slice is not configured

Expected results:
-----------------
gluster slice should be configured

Comment 2 SATHEESARAN 2019-03-06 11:57:24 UTC
Tested with gluster-ansible-features-1.0.4-5

Glusterfs slice is now available

[root@ ~]# systemctl status glusterd
● glusterd.service - GlusterFS, a clustered file-system server
   Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/glusterd.service.d
           └─99-cpu.conf
   Active: active (running) since Wed 2019-03-06 13:53:36 IST; 3h 30min ago
 Main PID: 5365 (glusterd)
   CGroup: /system.slice/glusterd.service
           ├─ 5365 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level IN...
           ├─ 9863 /usr/sbin/glusterfsd -s dhcp37-161.lab.eng.blr.redhat.com ...
           ├─10355 /usr/sbin/glusterfsd -s dhcp37-161.lab.eng.blr.redhat.com ...
           └─10377 /usr/sbin/glusterfs -s localhost --volfile-id gluster/glus...

Mar 06 13:53:31 dhcp37-161.lab.eng.blr.redhat.com systemd[1]: Starting Gluste...
Mar 06 13:53:36 dhcp37-161.lab.eng.blr.redhat.com systemd[1]: Started Gluster...
Mar 06 14:29:28 dhcp37-161.lab.eng.blr.redhat.com glusterd[5365]: [2019-03-06...
Mar 06 14:29:40 dhcp37-161.lab.eng.blr.redhat.com glusterd[5365]: [2019-03-06...

[root@ ~]# cat /etc/systemd/system/glusterfs.slice 
[Slice]
CPUQuota=200%

[root@ ~]# nproc
4

Comment 7 errata-xmlrpc 2019-05-09 06:09:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1121