Is your feature request related to a problem? Please describe
With remote store feature, we create and verify remote store repositories during node bootstrap. We have noticed that during remote store throttling, the node bootstrap fails and causes the node to get started successfully. This issue can be averted if we can reduce the occurrences of throttling.
Describe the solution you'd like
Drawing inspiration from #12567, we propose that we give ability for passing in a hash value just before the base path. This way we increase the scaling capabilities of the load that can be put onto the remote store.
Related component
Storage:Performance
Describe alternatives you've considered
The other alternate is that 1) we handle the exception and keep on retrying 2) get rid of verification for each node. While option 1 is doable and solves the issue to certain extent, option 2 does not seem rationale as the purpose of the create and verify repository step is to check accessibility.
Additional context
No response
Is your feature request related to a problem? Please describe
With remote store feature, we create and verify remote store repositories during node bootstrap. We have noticed that during remote store throttling, the node bootstrap fails and causes the node to get started successfully. This issue can be averted if we can reduce the occurrences of throttling.
Describe the solution you'd like
Drawing inspiration from #12567, we propose that we give ability for passing in a hash value just before the base path. This way we increase the scaling capabilities of the load that can be put onto the remote store.
Related component
Storage:Performance
Describe alternatives you've considered
The other alternate is that 1) we handle the exception and keep on retrying 2) get rid of verification for each node. While option 1 is doable and solves the issue to certain extent, option 2 does not seem rationale as the purpose of the create and verify repository step is to check accessibility.
Additional context
No response