Bug 1139183 - Older clients [ < RHS 3.0 ] should not be allowed to get connected even when rebalance is in progress
Summary: Older clients [ < RHS 3.0 ] should not be allowed to get connected even when ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribute
Version: rhgs-3.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Nithya Balachandran
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard: dht-pm-query
Depends On:
Blocks: 1087818
TreeView+ depends on / blocked
 
Reported: 2014-09-08 10:35 UTC by SATHEESARAN
Modified: 2023-09-14 02:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
The Red Hat Storage 3.0 version does not prevent clients with versions older Red Hat Storage 3.0 from mounting a volume on which rebalance is performed. Users with versions older than Red Hat Storage 3.0 mounting a volume on which rebalance is performed can lead to data loss.
Clone Of:
Environment:
Last Closed: 2017-08-30 08:17:18 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2014-09-08 10:35:34 UTC
Description of problem:
-----------------------
With RHS 3.0 Latest build ( glusterfs-3.6.0.28-1.el6rhs ), when the older clients ( less than RHS 3.0 ) mounts the distribute volume, rebalance operation was prohibited with error message "volume rebalance: vol: failed: Volume vol has one or more connected clients of a version lower than RHS-2.1 update 5. Starting rebalance in this state could lead to data loss.
Please disconnect those clients before attempting this command again."

But when the older client is connected, while rebalance already is in progress,
the client mount is accepted.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
glusterfs-3.6.0.28-1.el6rhs

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. With RHS 3.0, create a distribute volume with 2 bricks
2. Start the volume
3. Mount the volumes in RHS 3.0 client and add few files
4. Add more bricks to the volume
5. Perform rebalance
6. While rebalance is in progress, mount the volume from older client less than RHS 3.0

Actual results:
---------------
The mount in older client gets mounted successfully

Expected results:
-----------------
The older client mounting the volume and accessing it, while rebalance is in progress, could lead to data loss

Comment 3 Kaushal 2014-09-15 07:07:49 UTC
Added a known issue doc text.

Comment 4 Shalaka 2014-09-20 09:25:50 UTC
Please review and sign-off the edited doc text.

Comment 5 Shalaka 2014-09-26 05:49:08 UTC
Canceling need_info as the text was reviewed and signed-off during online review meeting.

Comment 7 Nithya Balachandran 2017-08-30 08:17:18 UTC
I am closing this BZ as RHGS 2.x is now EOL.

Comment 8 Red Hat Bugzilla 2023-09-14 02:47:09 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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