Bug 1255582 - Add the ability to force an unconditional graph reload
Add the ability to force an unconditional graph reload
Status: NEW
Product: GlusterFS
Classification: Community
Component: core (Show other bugs)
mainline
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-20 23:09 EDT by Joe Julian
Modified: 2016-02-17 19:25 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joe Julian 2015-08-20 23:09:21 EDT
On the rare occasion something is wrong, like the client will not reconnect to a brick, I've been able to work around it by changing a volume setting that affects the client. This causes the client to reload the vol file and return to sanity.

A kill -HUP does not do this as the client recognizes that the vol file hasn't changed and refuses to reload.

Adding the ability to force a reload may be beneficial perhaps a SIGUSR2?

I wouldn't rely on the glusterd connection and, in fact, the signal should force that reconnection as well.

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