-
Notifications
You must be signed in to change notification settings - Fork 14
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
Connection pools #189
base: development/v.0.0.2
Are you sure you want to change the base?
Connection pools #189
Conversation
Feature/extract debug
Separate files for UpstreamManager.
…ulti-threading request/response.
Some UpstreamManager bugs fixed.
0275013
to
7c9ad69
Compare
A host resolution test added. Host resolution errors are handled.
data/config.ini
Outdated
@@ -44,13 +45,17 @@ requests-per-sec=100 ;; maximal amount of requests per second in the window, 0 t | |||
ban-ip-sec=300 ;; time duration in seconds to ban particular IP, 0 to ban forever | |||
|
|||
[upstream] | |||
default=127.0.0.1:28681 | |||
blah=https://127.0.0.1:8080 | |||
walletnode=http://127.0.0.1:28694 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
format is very confusing and not self-explanatory, especially "keepAlive" - why just don't have it as last optional parameter? e.g.:
address[, timeout[, max_connections, [keep_alive]]]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, suggesting following format:
<name>=<uri>[,<timeout-in-seconds>[,<max-active-connections-per-upstream>],max-active-connections-per-address,]]keep-alive]]]
because connections limit and keep alive are unrelated entities and right now keepAlive
flag implicitly switches limit's scope (upstream limit vs address (aka unique host:port record))
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comma-separated values with variable number of arguments are horrible and non-descriptive. How about:
<name>=<uri>
<name>-timeout=seconds
<name>-max-conns-upstream=count
<name>-max-conns-address=count
<name>-keep-alive=seconds
27d5339
to
fc7a723
Compare
It includes #186