Deuxfleurs/garage
48
56
Fork 73
Code Issues 99 Pull requests 13 Releases 30 Wiki Activity

Clearer error message when LMDB has oom error (fix #517) #519

Merged
lx merged 1 commit from lmdb-oom-message into main 2023-03-06 10:49:04 +00:00
Conversation 2 Commits 1 Files changed 1 +10 -3
lx commented 2023-03-06 10:39:33 +00:00
Owner
Copy link
No description provided.
lx added 1 commit 2023-03-06 10:39:34 +00:00
Clearer error message when LMDB has oom error (fix #517)
All checks were successful
continuous-integration/drone/pr Build is passing
Details
continuous-integration/drone/push Build is passing
Details
b8123fb6cd
lx merged commit 0d0906b066 into main 2023-03-06 10:49:04 +00:00
lx deleted branch lmdb-oom-message 2023-03-06 10:49:05 +00:00
kryptonian commented 2023-03-07 05:52:04 +00:00
First-time contributor
Copy link

I think that error is still not sufficient. It should tell the user how much is the minium it has to allocate for it to function properly.

If it's not known how much it needs, there is no way to actually make proper limits that would allow it.

$ ulimit -v
67108864
$ ulimit -v unlimited
-bash: ulimit: virtual memory: cannot modify limit: Operation not permitted

If that virtual memory is not enough, then it would probably need optimization.

I think that error is still not sufficient. It should tell the user how much is the minium it has to allocate for it to function properly. If it's not known how much it needs, there is no way to actually make proper limits that would allow it. ``` $ ulimit -v 67108864 $ ulimit -v unlimited -bash: ulimit: virtual memory: cannot modify limit: Operation not permitted ``` If that virtual memory is not enough, then it would probably need optimization.
lx commented 2023-03-07 18:24:23 +00:00
Author
Owner
Copy link

If that virtual memory is not enough, then it would probably need optimization.

That's not how it works. LMDB needs to be able to map in RAM the entire file of the biggest possible database we want to support; concievably someone will someday use Garage with a metadata db bigger than 67GB. Currently the limit is set to 1TB (on 64-bit systems), we might raise it if needed but definitely not make it smaller. On 32-bit systems Garage tries to use a 1GB map size but it's wanky and LMDB should better be avoided on 32-bit systems.

> If that virtual memory is not enough, then it would probably need optimization. That's not how it works. LMDB needs to be able to map in RAM the entire file of the biggest possible database we want to support; concievably someone will someday use Garage with a metadata db bigger than 67GB. Currently the limit is set to 1TB (on 64-bit systems), we might raise it if needed but definitely not make it smaller. On 32-bit systems Garage tries to use a 1GB map size but it's wanky and LMDB should better be avoided on 32-bit systems.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
action
check-aws
The behaviour should be checked against AWS S3

  
action
discussion-needed
We need to discuss if the feature is desirable and/or better specify the envisioned behavior or technical implementation

  
action
for-external-contributors
Core team does not plan working on this in the near future however an external contribution will be reviewed & merged

  
action
for-newcomers
An issue that should be newcomer friendly.

  
action
more-info-needed
More information is needed to investigate this issue

  
action
need-funding
This issue represents lots of work, we need to find money to pay our core team work

  
action
triage-required
It's not very clear what we want to do with this issue yet, more thoughts is required

  
kind
correctness
Issues of theoretical correctness that may impact edge-case scenarios

  
kind
ideas
For abstract ideas/proposal to make Garage better, to better communicate our not yet achieved aims

  
kind
improvement
Feature requests that do not fall in other categories

  
kind
performance
Deceptive performance observed OR idea to improve performances

  
kind
testing
Functional tests, integration tests, Jepsen, etc.

  
kind
usability
Propositions to make Garage easier to operate, by improving error reporting, CLI, etc.

  
kind
wrong-behavior
Unintended behavior

  
prio
critical
Could impact integrity or availability of production clusters

  
prio
low
For issues that we don't want to spend time on until made absolutely necessary

  
scope
admin-api
Issues concerning the administration API

  
scope
background-healing
Background healing covers repair tasks, anti-entropy, merkle trees, etc. ; everything related to replicating data appropriately.

  
scope
build
Issues with Nix, Drone, Rust Compiler, etc.

  
scope
documentation

  
scope
k8s
Kubernetes related, including Helm Charts

  
scope
layout
Linked to the cluster layout and storage management

  
scope
metadata
Metadata Engine (LMDB, sqlite, etc.)

  
scope
ops
Operations related to operations/maintenance issue, tooling related (like CLI missing info ; impossible, too dangerous, too complicated migration, etc.)

  
scope
rpc
Linked to RPC

  
scope
s3-api
Related to the S3 API (especially compatibility issues).

  
scope
security
Cryptography-related, auth-related, authorization-related issues

  
scope
telemetry
OpenTelemetry (traces, metrics, etc.)

No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#519
No description provided.
Delete branch "lmdb-oom-message"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?