feat: one more queue for "external" requests from 3rd parties #6045
Conversation
knst
changed the title
|
Guix Automation has began to build this PR tagged as v21.0.0-devpr6045.984c7b35. A new comment will be made when the image is pushed. |
|
Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v21.0.0-devpr6045.984c7b35. The image should be on dockerhub soon. |
|
Is this a chore? It kinda seems like a feature. |
knst
changed the title
|
as noticed by shumkov@, need to have rpc's access to wallet, this approach won't work. <re-implementing...> |
…e to choose queue
|
Guix Automation has began to build this PR tagged as v21.0.0-devpr6045.c575a580. A new comment will be made when the image is pushed. |
|
Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v21.0.0-devpr6045.c575a580. The image should be on dockerhub soon. |
|
Guix Automation has began to build this PR tagged as v21.0.0-devpr6045.68def970. A new comment will be made when the image is pushed. |
|
Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v21.0.0-devpr6045.68def970. The image should be on dockerhub soon. |
|
Guix Automation has began to build this PR tagged as v21.0.0-devpr6045.241f0739. A new comment will be made when the image is pushed. |
|
Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v21.0.0-devpr6045.241f0739. The image should be on dockerhub soon. |
Describes the new "external user" queue from dashpay/dash#6045
* docs(api): update whitelist description * docs(rpc): deprecate platform user Related to dashpay/dash#6209 * docs(rpc): change example formatting * docs(rpc): add rpc queue info Describes the new "external user" queue from dashpay/dash#6045 * fix(rpc): correct code block type * style: filename * docs(rpc): link to whitelist settings from deprecated platform-user section
* docs(api): update whitelist description * docs(rpc): deprecate platform user Related to dashpay/dash#6209 * docs(rpc): change example formatting * docs(rpc): add rpc queue info Describes the new "external user" queue from dashpay/dash#6045 * fix(rpc): correct code block type * style: filename * docs(rpc): link to whitelist settings from deprecated platform-user section
5 participants
Issue being fixed or feature implemented
To avoid struggling to response to critical rpc requests, and split them from 3rd parties who uses a node as an external service, there are introduced one more queue of requests that will be served without throttling for instance consensus important rpcs
What was done?
new command line arguments:
rpcexternaluser- List of comma-separated usernames for JSON-RPC external connections. If not specified, there's no special queue is created, all requests in one queuerpcexternalworkqueue=<n>- Set the depth of the work queue to service external RPC callsHow Has This Been Tested?
Functional test
rpc_platform_filter.pyis updated to test new functionalityBreaking Changes
NA
Checklist: