glusterfs.git/extras/systemd, branch devel

extras/systemd: Move StartLimitIntervalSec to [Unit] section

2020-06-19T05:57:38+00:00

It has been a while since systemd moved[1] StartLimitInterval= and
StartLimitBurst= options(along with some others) from [Service] to
[Unit] section. Additionally StartLimitInterval= got renamed[2] to
StartLimitIntervalSec= and can be configured only in [Service] section.
Therefore making necessary modifications to avoid following warning:

$ sudo systemd-analyze verify glusterd.service
/usr/local/lib/systemd/system/glusterd.service:21: Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring.

For backward compatability reasons those options configured in [Service]
section are also honoured but officially documented in man
systemd.unit(5)[3].

[1] https://github.com/systemd/systemd/commit/6bf0f408e4833152197fb38fb10a9989c89f3a59
[2] https://github.com/systemd/systemd/commit/f0367da7d1a61ad698a55d17b5c28ddce0dc265a
[3] https://www.freedesktop.org/software/systemd/man/systemd.unit.html

Change-Id: I72a5b65930ddcf1d84c7e66f11685fa9a6fbda9a
Updates: #1000
Signed-off-by: Anoop C S

Use already expanded SYSCONF_DIR in glusterd.service instead of sysconfdir

2020-04-23T15:25:13+00:00

The generated glusterd.service file included the Automake artifact
`${prefix}` in the EnvironmentFile definition. When an actual value for
`${prefix}` is specified by Automake, this is not properly passed on
to glusterd.service's EnvironmentFile variable since `${prefix}` will
not be expanded once it is no longer in the control of Automake.

Because this artifact was left by the sysconfdir variable, we substitute
it with the SYSCONF_DIR variable that configure.ac expands earlier.

Change-Id: I980b27590c15facb567b153bd57078fed320ff87
Updates: #1135
Signed-off-by: Charles Celerier

glusterd: increase the StartLimitBurst

2020-01-07T10:02:13+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-11-25T11:05:42+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-13T05:42:02+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:35:20+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-04T05:47:21+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-01T13:03:12+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-01-30T08:54:14+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

2018-11-27T06:17:12+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