-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add new node and expand volume #696
Comments
Yes, your expectation is right.
It could be a bug. Upgrading to latest (near latest) releases always help. But please note that, if you are writing to same file which was present, then even if you do rebalance it wouldn't help. Did you notice any errors, or concerning logs in rebalance logs (or even in 'rebalance status' command)? |
I'm not keep writing files. I did a test: then found that new bricks have no data even the old bricks is full |
Thank you for your contributions. |
Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it. |
I use glusterfs 3.12.6
I add some nodes to my cluster, and expand a volume, and rebalance data
the volume have 3 bricks(replicate) on old nodes, after volume expand ,3 bricks added to new nodes
the client mount the volume before I add nodes to cluster
mount : mount -t glusterfs node:volumename /dir
then I write data to the volume,and find that the data only write to the bricks on old nodes,even after rebalance,even the brick is full
until I remount the volume
I think remount is unnecessary
is glusterfs‘s bug?or I should update version?
The text was updated successfully, but these errors were encountered: