Bug 857220 - [enhancement]: Add "system restart" command for managing version upgrades
[enhancement]: Add "system restart" command for managing version upgrades
Status: NEW
Product: GlusterFS
Classification: Community
Component: cli (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: ---
: ---
Assigned To: Kaushal
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-09-13 16:00 EDT by Joe Julian
Modified: 2016-01-11 03:46 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-22 11:46:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Julian 2012-09-13 16:00:01 EDT
The current sysvinit/upstart/systemd script method of restarting (or not restarting) glusterfsd instances (bricks) produces very high load if successful, or doesn't restart bricks at all leaving them running older versions.

I propose a new "system" command:

gluster system restart [target_load=2] [nfs=false]

It would gracefully kill single bricks, and re-spawn them, waiting to proceed to the next one until the system load fell below target_load. It would also kill and restart the self-heal daemon and if nfs=true, the nfs daemon. Once it's finished all of those, can it reload itself?
Comment 1 Kaleb KEITHLEY 2015-10-22 11:46:38 EDT
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.
Comment 2 Niels de Vos 2015-12-01 07:25:05 EST
Feature requests are only valid against the 'mainline' version. Once patches have been posted, it might be possible to get them backported, and at that time you can request a backport for a certain current version (clone this bug, or ask on irc/mailinglist).

Note You need to log in before you can comment on or make changes to this bug.