[Bugs] [Bug 1743988] New: Setting cluster.heal-timeout requires volume restart
bugzilla at redhat.com
bugzilla at redhat.com
Wed Aug 21 06:01:00 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1743988
Bug ID: 1743988
Summary: Setting cluster.heal-timeout requires volume restart
Product: GlusterFS
Version: 6
Hardware: x86_64
OS: Linux
Status: NEW
Component: selfheal
Severity: low
Assignee: bugs at gluster.org
Reporter: glenk1973 at hotmail.com
CC: bugs at gluster.org
Target Milestone: ---
Classification: Community
Description of problem:
Setting the `cluster.heal-timeout` requires a volume restart to take effect.
Version-Release number of selected component (if applicable):
6.5
How reproducible:
Every time
Steps to Reproduce:
1. Provision a 3-peer replica volume (I used three docker containers).
2. Set `cluster.favorite-child-policy` to `mtime`.
3. Mount the volume on one of the containers (say `gluster-0`, serving as a
server and a client).
4. Stop the self-heal daemon.
5. Set `cluster.entry-self-heal`, `cluster.data-self-heal` and
`cluster.metadata-self-heal` to off.
6. Set `cluster.quorum-type` to none.
7. Write "first write" to file `test.txt` on the mounted volume.
8. Kill the brick process `gluster-2`.
9. Write "second write" to `test.txt`.
10. Force start the volume (`gluster volume start <volume> force`)
11. Kill brick processes `gluster-0` and `gluster-1`.
12. Write "third write" to `test.txt`.
13. Force start the volume.
14. Verify that "split-brain" appears in the output of `gluster volume heal
<volume> info` command.
15. Set `cluster.heal-timeout` to `60`.
16. Start the self-heal daemon.
17. Issue `gluster volume heal <volume> info` command after 70 seconds.
18. Verify that the output at step 17 does not contain "split-brain".
19. Verify that the content of `test.txt` is "third write".
Actual results:
The output at step 17 contains "split-brain".
Expected results:
The output at step 17 should _not_ contain "split-brain".
Additional info:
According to what Ravishankar N said on Slack
(https://gluster.slack.com/archives/CH9M2KF60/p1566346818102000), changing
volume options such as `cluster.heal-timeout` should not require a process
restart. If I add a `gluster volume start <volume> force` command immediately
after step 16 above, then I get the Expected results.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list