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

What IP Address should we use when calling init method on ConnectionPool #245

Closed
porscheme opened this issue Dec 8, 2022 · 2 comments
Closed

Comments

@porscheme
Copy link

porscheme commented Dec 8, 2022

General Question

Can someone tell what IP Address should we use when calling init method on ConnectionPool

  • Should we use graph service NodePort IP Address?
  • Or, should we use IP Address of all graphd nodes?

Below code snippet is from official nebula-python release docs

# define a config
config = Config()
config.max_connection_pool_size = 10
# init connection pool
connection_pool = ConnectionPool()
# if the given servers are ok, return true, else return false
ok = connection_pool.init([('127.0.0.1', 9669)], config)

@wey-gu

@wey-gu
Copy link
Contributor

wey-gu commented Dec 8, 2022

Service IP is good, as session is the only stateful context here, for graphd(stateless), you could use one single service IP of all graphD(if they are Homogeneous), but also you could list all graphd nodes' IP.

In former case, the load-balancing was done by k8s service, and in latter case, it's load was balanced by the client side.

Please note this only applied to graphd, not for storaged/metad, which are stateful.

@QingZ11
Copy link

QingZ11 commented Jan 29, 2023

We have noticed that the issue you created hasn’t been updated for nearly a month, is this issue been resolved? If not resolved, can you provide some more information? If solved, can you close this issue?

Thanks a lot for your contribution anyway 😊

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

No branches or pull requests

3 participants