-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Rethinkdb suddenly status exited #6701
Comments
You found a bug in the clustering logic. |
are they releasing anytime soon fixes on this following issue? |
@kirvk548 No. |
@kirvk548 RethinkDB is now known as RebirthDB and once they release the next version (2.4.0), you should upgrade and create an issue for this on the new repo if you still have problems. 😄 |
Yeah, that's what I'm planning already after releasing their next version.
Thanks :D :D :D
…On Sun, Sep 9, 2018 at 4:15 PM Jeremy ***@***.***> wrote:
@kirvk548 <https://github.com/kirvk548> RethinkDB is now known as
RebirthDB and once they release the next version (2.4.0), you should
upgrade and create an issue for this on the new repo if you still have
problems.
😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6701 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADQZm8xvdYx9NP93rR5Fkvus22GN8duFks5uZM4igaJpZM4WHOHJ>
.
|
Hello @srh , |
No, the bug is in 2.3.6. |
Is it fixed in 2.3.7? If yes I would close this issue since there are 2.3.7 packages out on the download server though not for every distro, yet. |
No, it's not fixed. |
Hello Guys,
I'm just newbie to rethinkdb so i have to ask question about this issue.
We have a cluster of rethinkdb server with 5 nodes on it. All of a sudden, one or two of servers will have a status exited on it, only by restarting the service will make it returned to normal. RethinkDB servers are running on a container with Ubuntu 16.04.3 LTS (Xenial Xerus) installed on it, 4GB RAM, 512 swap and I've already set vm.swappiness=10 in my /etc/sysctl.conf
The question is what is the cause of the issue or any idea on it?
Attached screenshot is the error that i saw also with no idea what is happening on it
Thanks for your consideration guys!!
The text was updated successfully, but these errors were encountered: