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

poor performance caused by using gigabit ethernet #3843

Closed
FangJinhe opened this issue Jan 28, 2022 · 1 comment
Closed

poor performance caused by using gigabit ethernet #3843

FangJinhe opened this issue Jan 28, 2022 · 1 comment
Assignees
Labels
type/bug Type: something is unexpected
Milestone

Comments

@FangJinhe
Copy link

FangJinhe commented Jan 28, 2022

clusters are configured as follows:
192.168.15.8 - metad, graphd, storaged
192.168.15.9 - metad, graphd, storaged
192.168.15.10 - metad, graphd, storaged

192.168.15.8/192.168.15.9/192.168.15.10 are bound to 10 gigabit ethernet(万兆网卡), server 192.168.15.9 has a gigabit ethernet(千兆网卡)which has address 192.168.15.201. When the clusters start, nebula services of server 192.168.15.9 use 192.168.15.201, which not configured in conf files(conf files use 192.168.15.9). This causes very poor performance.

@FangJinhe FangJinhe added the type/bug Type: something is unexpected label Jan 28, 2022
@Sophie-Xie Sophie-Xie added this to the v3.2.0 milestone Apr 28, 2022
@Sophie-Xie Sophie-Xie added the need to discuss Solution: issue or PR without a clear conclusion on whether to handle it label Apr 28, 2022
@CPWstatic
Copy link
Contributor

Which service bound to the wrong ip?

@Sophie-Xie Sophie-Xie added priority/low-pri Priority: low and removed priority/low-pri Priority: low need to discuss Solution: issue or PR without a clear conclusion on whether to handle it labels May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

3 participants