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
As currently implemented, whenever a RocksDb instance is opened as Secondary, this leaves a new log file inside a randomly generated directory. This should be dealt with somehow. 馃槓
There are few things to consider:
Would it be okay to remove artifacts associated with a RocksDb instance immediately after its disposal? In this case, we would lose access to the log file.
On the other hand, if we don't remove any artifacts, depending on how often RocksDb would be opened as Secondary, the root directory structure along with its size may grow uncontrollably.
One approach would be to systematically clean the folder from the application side.
The text was updated successfully, but these errors were encountered:
As currently implemented, whenever a
RocksDb
instance is opened asSecondary
, this leaves a new log file inside a randomly generated directory. This should be dealt with somehow. 馃槓There are few things to consider:
RocksDb
instance immediately after its disposal? In this case, we would lose access to the log file.RocksDb
would be opened asSecondary
, the root directory structure along with its size may grow uncontrollably.The text was updated successfully, but these errors were encountered: