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

When the machine hosting FE has multiple network cards, FE fails to restart #53006

Open
elon-X opened this issue Nov 19, 2024 · 1 comment
Open
Labels
type/bug Something isn't working

Comments

@elon-X
Copy link

elon-X commented Nov 19, 2024

Steps to reproduce the behavior (Required)

a Docker process was started on the FE machine. When restarting the FE process, the FE process fails to start, and the error log is as follows
image

The reason is that the Docker process causes a new virtual network card to be added. When FE starts, it retrieves the machine's IP and port, and then verifies it against the IP and port stored in the meta metadata. By default, it only takes the first entry from the list, which in this case is the newly added virtual network card, causing the process to fail and exit immediately.

image image image

the possible solution should be to retrieve all local addresses and then iterate through them for validation.

Expected behavior (Required)

Real behavior (Required)

StarRocks version (Required)

3.3.0-19a3f66

@elon-X elon-X added the type/bug Something isn't working label Nov 19, 2024
@kevincai
Copy link
Contributor

https://docs.starrocks.io/docs/administration/management/FE_configuration/#priority_networks

priority_networks is what you are looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants