Repository navigation
[#79,#484] Limit parallel-write streams across all clients (main) - #501
Conversation
|
Rebased to resolve conflict. |
|
All non-OIDC tests pass. |
alanking
left a comment
There was a problem hiding this comment.
Just noting that we didn't just rename an existing configuration, but also added a new one which has the old name of the existing configuration. Will need to put that in big letters for the release notes
Correct. The inclusion of
Agreed. |
|
Squashed. Please eyeball commit messages for typos, grammar. |
alanking
left a comment
There was a problem hiding this comment.
Just had one suggestion on wording...
On "Limit parallel-write streams across all clients":
"Exceeding this limit..." might sound better than "Violating this limit..."
|
Updated commit message. |
|
Oops, # it |
This commit adds a new configuration property and re-purposes an
existing one.
- max_number_of_parallel_write_streams
Limits how many streams can be reserved by the HTTP API, across all
clients. Exceeding this limit will result in an HTTP status code of
503 (Service Unavailable).
Before this commit, this property served the same purpose as the new
property (shown below).
- max_number_of_streams_per_parallel_write_handle
Limits how many streams can be associated to a single parallel-write
handle. Exceeding this limit will result in an HTTP status code of
400 (Bad Request).
Administrators will need to update their configuration on upgrade.
|
Added pounds. |
All tests pass.