Re: systemd kill mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Amar,

I am fairly new here, but am in constant communication with Strahil and would also like to mention he has helped me greatly on many occasions with his guidance and knowledge with GLUSTER....he rocks !

Thank you Strahil.

Regards,

Adrian

On Thu, Sep 3, 2020 at 11:37 PM Amar Tumballi <amar@xxxxxxxxx> wrote:
[Off topic]

On Thu, Sep 3, 2020 at 8:30 PM Strahil Nikolov <hunter86_bg@xxxxxxxxx> wrote:
I'm not a gluster developer

Wanted to take time to appreciate your efforts to make sure the users of Gluster are happy!

Strahil, you are doing a wonderful job to keep a opensource project progress. Users like you make up for community (and thanks to many others who take time to respond to fellow users)! Thank you :-)

Regards,
Amar

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@xxxxxxxxx> написа:





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.


Ward
________



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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
________



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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users


--
--
Container Storage made easy!

________



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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users


--
Adrian Quintero
________



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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux