getdozer / getdozer/dozer

Dynamic sizing of LMDB max map size

Open
#1,925 0 comments 0 reactions 1 assignee Claimed by @chubei View on GitHub
Dominant language
Rust
Stars
1.6k
Forks
145
PR merge metrics
No merged PRs in 30d

Description

We are currently facing issues in cloud due to the max map size of LMDB. One approach we could test is to start with a small number, and, when the database fails to write because it has exhausted all teh space, close and reopen the database file with a bigger number.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.