In the current implementation, we seem to store the required rf for a tablet/table in the master layer. May be it is better to additionally store/move this info into the consensus layer to make better decisions for all other consensus operations.
Once this is done, we also need to ensure that any changes to RF are still allowed, propagated down to consensus layer properly and are factored in when making changes to config.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information
[X] I confirm this issue does not contain any sensitive information.
@lingamsandeep , Lowering the priority to medium for now. As we discussed offline that we will pick it up at a later point, as split brain cannot happen.
Jira Link: DB-8256
Description
In the current implementation, we seem to store the required rf for a tablet/table in the master layer. May be it is better to additionally store/move this info into the consensus layer to make better decisions for all other consensus operations.
Once this is done, we also need to ensure that any changes to RF are still allowed, propagated down to consensus layer properly and are factored in when making changes to config.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information