Description
The standby instance size can increase due to the continuous sync process, and there's currently no way to run a cleanup operation.
This only gets worse when running compaction on the primary, the standby finds a new head state and starts pulling in all the changes effectively doubling (size = old standby size + primary size) the size of the store.
Attachments
Issue Links
- is related to
-
OAK-2817 TARMK Cold Standby cleanup removes too many binary segments
- Closed