glusterfs.git/extras/systemd, branch v9dev

glusterd: increase the StartLimitBurst

2020-01-08T15:04:08+00:00

Based on https://bugzilla.redhat.com/show_bug.cgi?id=1782200#c6
increasing the limit.

fixes: bz#1782200

Change-Id: Ia885c7bdb2a90f0946c5268da894f6a4da5a69b7
Signed-off-by: Sanju Rakonde

glusterd: start glusterd automatically on abnormal shutdown

2019-12-05T07:47:12+00:00

If glusterd crashes or goes down abnormally, systemd should
automatically bring the glusterd up.

With this change, systemd brings glusterd up for atmost 3 times
within time period of 1 hour. If the limit exceeds, we have to
start the glusterd manually and reset the failure count using
systemctl reset-failed.

credits: John Strunk 

fixes: bz#1776264

Change-Id: I312d243652fb13ba028814a2ea615b67e3b10b6a
Signed-off-by: Sanju Rakonde

extras: fix the remote subvol name in case of thin-arbiter

2019-11-16T09:07:39+00:00

* Also make sure to provide log-level in systemd file,
  instead of volfile itself.

Updates: bz#1193929
Change-Id: I45a0b0ff3ebb4b3e095b4eed14b7bdf5816926d0
Signed-off-by: Amar Tumballi

glusterd: glusterd service is getting timed out on scaled setup

2019-08-28T03:44:49+00:00

Problem: On a three node cluster with 2000 replica volumes systemctl is getting
         timed out for glusted service.

Solution: Configure TimeoutSec 300 to wait for glusterd startup.

Change-Id: Idb3f3f3e56e6216a0ebd754cbb9e8e37ce9e636d
Fixes: bz#1746228
Signed-off-by: Mohit Agrawal

cluster/replicate: Modify command in unit file to assign port correctly

2019-06-08T05:39:10+00:00

Problem:
In unit file of TA process we have been using ta-vol as
volume id and also ta-vol-server.transport.socket.listen-port=24007

In volume file for TA process we only consider volname
as "ta" and not as "ta-vol". That's why it was not able to assign
this port number to ta process as in volume file it will try to
find server xlator as ta-vol

volume ta-server  <<<<<<<<< not ta-vol-server
 46     type protocol/server
 47     option transport.listen-backlog 10
 48     option transport.socket.keepalive-count 9
 49     option transport.socket.keepalive-interval 2
 50     option transport.socket.keepalive-time 20
 51     option transport.tcp-user-timeout 0
 52     option transport.socket.keepalive 1
 53     option auth.addr./mnt/thin-arbiter.allow *
 54     option auth-path /mnt/thin-arbiter
 55     option transport.address-family inet
 56     option transport-type tcp
 57     subvolumes ta-io-stats
 58 end-volume

Solution:
Provide "ta" as vol id for the  command which Unit file
is going to execute.

Also, made changes in setup-thin-arbiter.sh to correctly
identify the directory of Unit file irrespective of the location from
where we are executing this script.

Change-Id: Ia7bbccdc0304e7dfaaa732bebb726fba731d1d33
fixes: bz#1716766
Signed-off-by: Ashish Pandey

build: conditional rpcbind for gnfs in glusterd.service

2019-04-23T11:45:44+00:00

Don't Require: rpcbind in glusterd.service when gnfs isn't built

Also add .../gluster-ta-volume.service to .gitignore

See https://github.com/gluster/glusterfs/issues/647

Change-Id: I4d90cf66b12c378c0a9aace89a3a4bbf3784c284
Fixes: #647
Signed-off-by: Kaleb S. KEITHLEY

rpm: add thin-arbiter package

2019-03-11T04:05:34+00:00

Discussion on thin arbiter volume -
https://github.com/gluster/glusterfs/issues/352#issuecomment-350981148

Main idea of having this rpm package is to deploy thin-arbiter
without glusterd and other commands on a node, and all we need
on that tie-breaker node is to run a single glusterfs command.
Also note that, no other glusterfs installation needs
thin-arbiter.so.

Make sure RPM contains sample vol file, which can work by default,
and a script to configure that volfile, along with translator image.

Change-Id: Ibace758373d8a991b6a19b2ecc60c93b2f8fc489
updates: bz#1674389
Signed-off-by: Amar Tumballi 
Signed-off-by: Ashish Pandey

extras/systemd: Remove socket activated syslog.target and add documentation keys

2019-01-11T07:30:06+00:00

Adopting patch provided by Patrick Matthäi  at:

https://bugzilla.redhat.com/attachment.cgi?id=1470751

fixes: bz#1560561
Change-Id: I363a049c743c65823e6c4f153cbe20b47fcb64fb
Signed-off-by: Vijay Bellur

build: add --without-server option

2018-02-19T17:38:55+00:00

With Gluster 4.0 we will not provide the server components for EL6 and
older. At one point Gluster 4.x will get GlusterD2, which requires
Golang tools in the distribution. EL6 does not contain these at the
moment.

With this change, it is possible to `./configure --without-server` which
prevents building glusterd and the xlators for the bricks. Building RPMs
can pass `--without server` and the glusterfs-server sub-package will
not be created.

Change-Id: I97f5ccf9f2c76e60d9af83915fc59fae57ad6d25
BUG: 1074947
Signed-off-by: Niels de Vos

systemd/glusterfssharedstorage : remove dependency for var-run-gluster-shared_storage

2017-07-17T11:41:00+00:00

Currently the script used by glusterfssharedstorage have dependency over
var-run-gluster-shared_storage. But this service will be present only if
node has rebooted. Also in reboot scenario , there is a chance that this
service can be executed before creating var-run-gluster-shared_storage.
In that case glusterfssharedstorage will get succeed even without mounting
the shared storage

Also the type of glusterfssharedstorage changed to "forking" so that it can
be active(instead of dead) after the successful start.

Change-Id: I1c02cc64946e534d845aa7ec7b72644bbe4d26f9
BUG: 1452527
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/17658
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY