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

If we configure more than one clusters in conf.yaml, the timeout field of former cluster will be overridden #189

Closed
alchemy-lee opened this issue Jun 15, 2021 · 0 comments · Fixed by #190
Closed

If we configure more than one clusters in conf.yaml, the timeout field of former cluster will be overridden #189

alchemy-lee opened this issue Jun 15, 2021 · 0 comments · Fixed by #190

Comments

@alchemy-lee
Copy link
Contributor

What happened:

If we configure more than one cluster in conf.yaml, the timeout field (connect_timeout and request_timeout) of the former cluster will be overridden.

Solution:

We can move the timeout config outside the clusters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix timeout config overridden alchemy-lee/dubbo-go-pixiu
1 participant
@alchemy-lee