-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant open leveldb file #1869
Comments
Added a fix. The nil happened when volume loading failed. But it is not clear why the volume loading failed. The "resource temporarily unavailable" is not very clear. |
|
ok sweet!
…On Sun, Mar 7, 2021 at 8:44 PM Peter Cai ***@***.***> wrote:
resource temporarily unavailable is normally related to limits on open
file handles or nprocs. This would also explain why the failure seems
random.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1869 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTCFZID7TUUY4MSJGONAWLTCNYLHANCNFSM4YXUX6VA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm using the official helm deployment and set the volume server replica to 2. It was working well with memory index for volume server but when I change it to leveldb, some pods randomly failed and keep the failure status forever. The log I got is below:
But some pods are working fine. Screenshot as below:
System Setup
List the command line to start "weed master", "weed volume", "weed filer", "weed s3", "weed mount".
I'm using the helm charts
OS version
Ubuntu 18.04 with k8s 1.20.0
output of
weed version
2.23
if using filer, show the content of
filer.toml
IDK where is this file.
Expected behavior
It should work smoothly
The text was updated successfully, but these errors were encountered: