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.

Sign up for GitHub

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

Jump to bottom

connected to the volfile server too long time when cluster have many node and mount server glusterd restart #4442

Closed
shenwen2012 opened this issue Dec 19, 2024 · 1 comment · Fixed by shenwen2012/glusterfs#1 · May be fixed by #4443
Closed

connected to the volfile server too long time when cluster have many node and mount server glusterd restart #4442

shenwen2012 opened this issue Dec 19, 2024 · 1 comment · Fixed by shenwen2012/glusterfs#1 · May be fixed by #4443

Comments

@shenwen2012
Copy link

Description of problem:
when cluster have many nodes 100, if you mounst -t glusterfs localhost:volname /mnt , localhost glusterd restart , will long time can not connect glusterd. beause client will test connect to other node glusterd, but connect ,socket bind localhost ,so it can not connect other node glusterd. it try connect other 99 node then connect localhost glusterd ,so will be too long time.

The exact command to reproduce the issue:

The full output of the command that failed:

Expected results:

Mandatory info:
- The output of the gluster volume info command:

- The output of the gluster volume status command:

- The output of the gluster volume heal command:

**- Provide logs present on following locations of client and server nodes -
/var/log/glusterfs/

**- Is there any crash ? Provide the backtrace and coredump

Additional info:

- The operating system / glusterfs version:

Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration
@shenwen2012
Copy link
Author

shenwen2012 commented Dec 19, 2024 •
edited
Loading

solve this problem:
when glusterd is down , client change connect glusterd server ,add a if strncmp(local_str,rpc_trans->myinfo.identifier,strlen(local_str)), local_str ="127.0.0.1"
if mount server ip addr is 127.0.0.1 or localhost should not change connect glusterd server,beause it only can connect sucess localhost glusterd. modify on this commit c2d1fa5#diff-8e9a4103e4eb659a9277b69d6b824a195a919df31ea2a384807e3a2444680064R2832

shenwen2012 added a commit to shenwen2012/glusterfs that referenced this issue Dec 19, 2024
@shenwen2012
change connect glusterd addr filter localhost (gluster#4442)
01f8c2a 
when use localhost(127.0.0.1)  addr mount a volume,  if glusterd is down ,client not change  connect other glusterd server , because socket bind  127.0.0.1 can not connect other node addr success .
so change volume server round-roubin  filter  127.0.0.1 

Fixes: gluster#4442

Signed-off-by: tanshiping <[email protected]>
@shenwen2012 shenwen2012 mentioned this issue Dec 19, 2024
Merged
shenwen2012 added a commit to shenwen2012/glusterfs that referenced this issue Dec 20, 2024
@shenwen2012
Merge pull request #1 from shenwen2012/filter-localhost-round-robin-g…
92131a2 
…lusterd-server

change connect glusterd addr filter localhost (gluster#4442)
@shenwen2012 shenwen2012 mentioned this issue Dec 20, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@shenwen2012