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

There are some limitations to the distributed network connection #35

Open
nlighting opened this issue Jul 13, 2023 · 0 comments · May be fixed by #36
Open

There are some limitations to the distributed network connection #35

nlighting opened this issue Jul 13, 2023 · 0 comments · May be fixed by #36
Assignees
@nlighting
Labels
enhancement New feature or request

Comments

@nlighting
Copy link
Collaborator

Currently, when a hiactor cluster needs to be started, the order in which the nodes are started must be strictly in accordance with their machine id order. The reason is: The current connection rule is that a node with a larger machine id will act as a client to connect to a node with a smaller machine id. If the node with a smaller machine id has not been started at this time, a connection error will occur.

image
@nlighting nlighting added the enhancement New feature or request label Jul 13, 2023
@nlighting nlighting self-assigned this Jul 13, 2023
@nlighting nlighting linked a pull request Jul 13, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nlighting nlighting

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support for more friendly distributed network connections nlighting/hiactor
1 participant
@nlighting