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
Given that almost all the users have upgraded to the version that supports a separate protocol (as/1) for active sets, we can disallow activeset fetching using hs/1 (normal hash protocol) to avoid possible overload scenarios, in which activeset requests are subject to normal hash blob pacers.
Steps to reproduce
Request activesets using hs/1 protocol
Actual Behavior
Requests succeed, subject to hs/1 pacer setting
Expected Behavior
Activesets not allowed to be fetched via hs/1, only via as/1
The text was updated successfully, but these errors were encountered:
Description
Given that almost all the users have upgraded to the version that supports a separate protocol (
as/1
) for active sets, we can disallow activeset fetching usinghs/1
(normal hash protocol) to avoid possible overload scenarios, in which activeset requests are subject to normal hash blob pacers.Steps to reproduce
Request activesets using
hs/1
protocolActual Behavior
Requests succeed, subject to
hs/1
pacer settingExpected Behavior
Activesets not allowed to be fetched via
hs/1
, only viaas/1
The text was updated successfully, but these errors were encountered: