Skip to content

Conversation

@simonmar
Copy link
Collaborator

From the comment:

 // LMDB needs us to pre-set the memory map size, which determines
 // the maximum size of the DB. Setting it to zero uses the mapsize
 // when the DB was created, while setting it to a value smaller than
 // the actual size of the DB causes LMDB to use the DB size - this
 // is what we want for a read-only DB. For a read/write DB we have
 // to pick a huge value, because the mapsize can only be increased
 // if there are no transactions in progress, and we don't have a good
 // way to do that aside from closing and re-opening the DB.

@netlify
Copy link

netlify bot commented Jan 22, 2026

Deploy Preview for fb-oss-glean canceled.

Name Link
🔨 Latest commit e2059c5
🔍 Latest deploy log https://app.netlify.com/projects/fb-oss-glean/deploys/69728873c5eb990008a7d478

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 22, 2026
@simonmar simonmar force-pushed the lmdb-10 branch 2 times, most recently from 45563b6 to 36f8f55 Compare January 22, 2026 15:11
@iamirzhan
Copy link
Contributor

iamirzhan commented Jan 22, 2026

ah, I am trying to run indexer internally and get [MDB_MAP_FULL](lmdb: MDB_MAP_FULL: Environment mapsize limit reached)` I guess that's why

@meta-codesync
Copy link
Contributor

meta-codesync bot commented Jan 22, 2026

@iamirzhan has imported this pull request. If you are a Meta employee, you can view this in D91237978.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants