[Gluster-users] systemd kill mode

Strahil Nikolov hunter86_bg at yahoo.com
Thu Sep 3 15:00:15 UTC 2020

I'm not a gluster developer and I haven't taken that decision.
As we are talking about storage - it's better to play safe and avoid any risks . Imagine a distributed volume and you restart the service instead of reload ... Data will be unavailable and the situation can go ugly.

Best Regards,
Strahil Nikolov

В четвъртък, 3 септември 2020 г., 10:11:42 Гринуич+3, Ward Poelmans <wpoely86 at gmail.com> написа: 

Hi Strahil,

On 2/09/2020 21:30, Strahil Nikolov wrote:

> you shouldn't do that,as it is intentional - glusterd is just a management layer and you might need to restart it in order to reconfigure a node. You don't want to kill your bricks to introduce a change, right? 

Starting up daemons in one systemd unit and killing them with another is
a bit weird? Can't a reconfigure happen through a ExecReload? Or let the
management daemon and the actual brick daemons run under different
systemd units?

> In CentOS there is a dedicated service that takes care to shutdown all processes and avoid such freeze .

Thanks, that should fix the issue too.


Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users at gluster.org

More information about the Gluster-users mailing list