-
Notifications
You must be signed in to change notification settings - Fork 635
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
Evenstore kept in unhealthy state after SIGABRT due to Out of Memory #1481
Comments
I have the same issue. Did you ever get any feedback on this? |
Nope |
@drozzy @uglywizkid we're very sorry for the delay. Based on some recent feedback we've identified with the help of one of our customers that mono 4.6 had some GC hanging issues when running low on memory. with tests on mono 4.8, the GC hanging issues were gone. we're looking at moving to mono 5 in the near future, this should in principle fix the above issues. |
So... which version is the docker file using @shaan1337 ? And is there any way I can switch it to 4.8? https://hub.docker.com/r/eventstore/eventstore/~/dockerfile/ Thanks |
It seems like 16.04 Ubuntu is using Mono 4.2 (am I right?)... which is what Docker image is based on: |
@drozzy The binary in our ubuntu package ( Here are the steps:
Please note that we also haven't heavily tested EventStore on mono 4.8 yet so it may be risky (we're planning to move directly to 5.x) |
@drozzy Increasing the amount of memory allocated to the container should resolve these issues though. You can also decrease number of cached chunks (2 by default = 512 MB), please see options: |
Thanks @shaan1337 , I'm looking at command line options, and I don't see the default of The default (I filed an issue with docs to improve the unit descriptions: https://github.com/EventStore/docs.geteventstore.com/issues/277) |
Setting Please advise. |
How did you set it?
…On Tue, Sep 4, 2018 at 5:01 AM Andriy Drozdyuk ***@***.***> wrote:
Setting CACHED_CHUNKS=0 did *nothing*, I'm still getting the same error
message... :(
Please advise.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1481 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAXRWpcYno-Zl8uRfwj8Jon1Gtyg9Sq4ks5uXfsvgaJpZM4QS74G>
.
--
Studying for the Turing test
|
With env variable as : EVENSTORE_CACHED_CHUNKS=0 Inside my docker swarm stack yml file. |
When starting up EventStore prints out its configuration (and where it got varying things from). Is it printing your configuration option as being set? |
Looks like it. Maybe it has something to do with Here is partial output:
|
First out of memory message is:
Looks like full 2 hours after the start. |
Here is my Docker stack file (the
|
@drozzy EventStore V5 is now on a new version of mono, is this still an issue? |
Sorry guys I haven't been on ES project for a while now. |
We are currently running the EventStore in a docker environment (https://github.com/EventStore/eventstore-docker). As the docker container run out of memory we got the following log output:
This seemed to have happened while EventStore was trying to gather information from the operating system for monitoring and stats.
Now the issue we faced, is that the EventStore kept running in an unhealthy state after this exception, instead of terminating all processes and letting docker to stop or even restart the container.
Probably there needs to be a better exception handling for exceptions returned by the ShellExecutor.cs. Currently, if I see it right, all exceptions are swallowed (e.g. in EsDriveInfo.cs).
Any help would be very appreciated.
The text was updated successfully, but these errors were encountered: