This repository has been archived by the owner on Mar 26, 2020. It is now read-only.
glustershd needs to be restarted for volume start/stop operations #1459
Assignees
Comments
atinmu
pushed a commit
to atinmu/glusterd2
that referenced
this issue
Jan 3, 2019
glustershd process needs to be restarted for every volume start/stop operations to ensure that glustershd can run with the latest volfiles. Currently due to the lack of client graph switch issue, a reconfigure isn't possible for such case with out a restart. volume set operation is still a TODO item and this PR doesn't cover this. Fixes: gluster#1459 Signed-off-by: Atin Mukherjee <[email protected]>
atinmu
added
bug
priority: high
GCS/1.0
|
glustershd will not be enabled with GCS/1.0. client side self heal can still heal the files in case there's a catch up to do when such a file under question is accessed from the mount point. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Based on code reading, it was found that glustershd wasn't restarted on volume start/stop operations which was resulting shd process to not having the latest volfile and it was continuing to attempt to connect to the stale bricks and GD2 logs were flooding with
time="2019-01-03 15:43:09.300668" level=info msg="client disconnected" address="172.17.0.4:996" server=sunrpc source="[server.go:109:sunrpc.(*SunRPC).pruneConn]"
time="2019-01-03 15:43:09.815217" level=info msg="client connected" address="172.17.0.3:996" server=sunrpc source="[server.go:148:sunrpc.(*SunRPC).acceptLoop]" transport=tcp
time="2019-01-03 15:43:09.818169" level=error msg="registry.SearchByBrickPath() failed for brick" brick=/tmp/b1 error="SearchByBrickPath: port for brick /tmp/b1 not found" source="[rpc_prog.go:104:pmap.(*GfPortmap).PortByBrick]"
The text was updated successfully, but these errors were encountered: