You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently http-max-response-time-ms is enforced only for the time required to convert the http response to JSON. Many/most http requests such as /v1/chain/get_table_rows have hard-coded time restrictions of 10ms.
Change all http requests to honor http-max-response-time-ms for complete time for handling the http request including time to retrieve data and convert to JSON.
This will give greater control to API operators and also allow locally running nodeos to set unlimited time. Note, however, if allowed to set to large values this can impact block production window times and speculative execution of incoming blocks. A node operator could set http-max-response-time-ms to a large value and then tie up the main thread for large amounts of time handling http requests impacting block production and block validation.
Currently
http-max-response-time-ms
is enforced only for the time required to convert the http response to JSON. Many/most http requests such as/v1/chain/get_table_rows
have hard-coded time restrictions of 10ms.Change all http requests to honor
http-max-response-time-ms
for complete time for handling the http request including time to retrieve data and convert to JSON.This will give greater control to API operators and also allow locally running nodeos to set unlimited time. Note, however, if allowed to set to large values this can impact block production window times and speculative execution of incoming blocks. A node operator could set
http-max-response-time-ms
to a large value and then tie up the main thread for large amounts of time handling http requests impacting block production and block validation.Related EOSIO/eos#10560
The text was updated successfully, but these errors were encountered: