Skip to content
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

Closed
wqy0812 opened this issue Jul 25, 2019 · 4 comments
Closed

add new node and expand volume #696

wqy0812 opened this issue Jul 25, 2019 · 4 comments
Labels
Question wontfix Managed by stale[bot]

Comments

@wqy0812
Copy link

wqy0812 commented Jul 25, 2019

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?

@amarts
Copy link
Member

amarts commented Oct 17, 2019

I think remount is unnecessary

Yes, your expectation is right.

is glusterfs‘s bug?or I should update version?

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)?

@wqy0812
Copy link
Author

wqy0812 commented Oct 22, 2019

I'm not keep writing files. I did a test:
process:
dd if=/dev/zero of=test bs=1M count=xxxx
expand cluster
expand volume
rebalance volume
dd if=/dev/zero of=test bs=1M count=xxxx

then found that new bricks have no data even the old bricks is full
I haven't tried the new version yet

@stale
Copy link

stale bot commented May 19, 2020

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

@stale stale bot added the wontfix Managed by stale[bot] label May 19, 2020
@stale
Copy link

stale bot commented Jun 3, 2020

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.

@stale stale bot closed this as completed Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question wontfix Managed by stale[bot]
Projects
None yet
Development

No branches or pull requests

2 participants