Bug 1540659 - Introduce lock recovery options to prevent possible post-upgrade mount failures
Summary: Introduce lock recovery options to prevent possible post-upgrade mount failures
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Anoop C S
QA Contact:
Depends On:
Blocks: 1540660
TreeView+ depends on / blocked
Reported: 2018-01-31 16:23 UTC by Shyamsundar
Modified: 2019-11-18 06:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1540660 (view as bug list)
Last Closed: 2019-11-18 06:42:58 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Description Shyamsundar 2018-01-31 16:23:41 UTC
This patch: https://review.gluster.org/12363 removes the following options,

Current worry is that if a volume has these options enabled, we would post-upgrading the server fail for client mounts (or even in other places). Also, removing these options post-upgrade may fail, as the options are not available, and hence may need editing the vol files.

We need to test and ensure that the above occurs, and if it does, we need to fix the situation in consultation with the glusterd team.

Current thoughts for fixing this up is to add these options back but as No-Ops, such that post upgrade functionality is removed, but the presence of the option itself does not cause failures.

Comment 1 Anoop C S 2019-11-18 06:42:58 UTC
We haven't had any complaints/issues for ~2 years around this volume options during upgrade. Moreover the dependent bug reported on v4.0 is no longer supported and was closed long back.

Thus closing this bug report on mainline version.

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