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

configservice前面如果已经有nginx做负载均衡了,为什么后面还需要通过meta server获取configservice的ip+port直连获取配置,不使用client端直接访问nginx域名获取配置? #2709

Closed
linian365boy opened this issue Oct 30, 2019 · 4 comments
Labels

Comments

@linian365boy
Copy link

linian365boy commented Oct 30, 2019

想知道这块设计的原因。portal 访问adminservice也是类似情况。

@linian365boy linian365boy changed the title configservice前面如果已经有nginx做负载均衡了,为什么后面还需要通过meta server获取configservice的ip+port直连获取配置,不使用client端不直接访问nginx域名获取配置? configservice前面如果已经有nginx做负载均衡了,为什么后面还需要通过meta server获取configservice的ip+port直连获取配置,不使用client端直接访问nginx域名获取配置? Oct 30, 2019
@nobodyiam
Copy link
Member

see #2155

@linian365boy
Copy link
Author

ok thanks

@stale
Copy link

stale bot commented Dec 30, 2019

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in 14 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 30, 2019
@stale
Copy link

stale bot commented Jan 13, 2020

This issue has been automatically closed because it has not had activity in the last 14 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants