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 storage node sync only uses nodes from the current storage committee. Instead, it should be also able to use (maybe with a lower priority) other storage nodes registered for the runtime to increase availability as certain runtime configurations (e.g., using a storage committee of size 1) make it more likely that the active committee does not have the required roots.
This should be backwards compatible and backported to the 20.11.x stable branch.
The text was updated successfully, but these errors were encountered:
Currently storage node sync only uses nodes from the current storage committee. Instead, it should be also able to use (maybe with a lower priority) other storage nodes registered for the runtime to increase availability as certain runtime configurations (e.g., using a storage committee of size 1) make it more likely that the active committee does not have the required roots.
This should be backwards compatible and backported to the 20.11.x stable branch.
The text was updated successfully, but these errors were encountered: