istae
istae
We are not planning to have this feature in the near future. We can reopen it if further discussion is needed at any point in the future.
in the case of the upcoming migration of the localstore rewrite, this should be taken into consideration.
have we seen any instances where the logging is a bottleneck?
Since it is actually possible to retrieve single chunks using the /stewardship endpoint, we will for now close this issue.
I see the point now. No, we do not have a query for this yet. It should be trivial to add though.
- The batchstore should just contain the list of batches, and calculate the reserve radius, and calls UnreserveBatch when the batch expires. - The new reserve will maintain the storage...
> This sharky implementation does not have guaranties which shard and location is returned next. As an outcome this could lead to 1) probably more cache invalidation (on hdd/ssd level);...
there are currently 6 workers in the `ReserveSample` function so this is a parallelized process. We can do with more profiling though to see where we can improve
A reasonable way to whitelist an address is to set it with a config option.