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

The meta_server_addrs in the configuration should support the host name. #931

Closed
monadbobo opened this issue Sep 11, 2019 · 0 comments · Fixed by #935
Closed

The meta_server_addrs in the configuration should support the host name. #931

monadbobo opened this issue Sep 11, 2019 · 0 comments · Fixed by #935
Assignees

Comments

@monadbobo
Copy link
Contributor

The meta_server_addrs in the configuration should support the host name.

@monadbobo monadbobo self-assigned this Sep 11, 2019
monadbobo added a commit to monadbobo/nebula that referenced this issue Sep 12, 2019
…port the host name.

Modify the toHostAddr interface to support host resolved (gethostbyname).
dutor pushed a commit that referenced this issue Dec 19, 2019
…me). (#935)

* Issue #931 the "meta_server_addrs" in the configuration support the host name.

Modify the toHostAddr interface to support host resolved (gethostbyname).

* replace the gethostbyname with getaddrinfo.

* Refactoring part of the code.
tong-hao pushed a commit to tong-hao/nebula that referenced this issue Jun 1, 2021
…me). (vesoft-inc#935)

* Issue vesoft-inc#931 the "meta_server_addrs" in the configuration support the host name.

Modify the toHostAddr interface to support host resolved (gethostbyname).

* replace the gethostbyname with getaddrinfo.

* Refactoring part of the code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant