Skip to content

Does the BlobDB still not support secondary instance? #13296

Open
@yunxiao3

Description

In the RocksDB wiki (https://github.com/facebook/rocksdb/wiki/BlobDB), it is stated that BlobDB does not support secondary instances. However, the specific reason for this lack of support isn't clearly explained.

Based on my understanding, due to the multi-version design of RocksDB, the primary instance cannot perceive references to some data (such as SST files and keys) that might be actively used by the secondary instance during compaction operations. This can lead to situations where data referenced by the secondary instance is inadvertently released by the primary instance. Blob files, which are also referenced by SST files, might be subject to the same issue.

I would like to know if there are other limitations, aside from the ones mentioned above, that prevent BlobDB from supporting secondary instances.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions