Skip to content
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

Open
kirvk548 opened this issue Aug 22, 2018 · 10 comments
Open

Rethinkdb suddenly status exited #6701

kirvk548 opened this issue Aug 22, 2018 · 10 comments

Comments

@kirvk548
Copy link

kirvk548 commented Aug 22, 2018

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

error-rethinkdb

Thanks for your consideration guys!!

@srh
Copy link
Contributor

srh commented Aug 22, 2018

You found a bug in the clustering logic.

@kirvk548
Copy link
Author

kirvk548 commented Sep 5, 2018

are they releasing anytime soon fixes on this following issue?

@grantcarthew
Copy link

https://github.com/RebirthDB/rebirthdb

@srh
Copy link
Contributor

srh commented Sep 7, 2018

@kirvk548 No.

@Extarys
Copy link

Extarys commented Sep 9, 2018

@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.

😄

@kirvk548
Copy link
Author

kirvk548 commented Sep 17, 2018 via email

@gabor-boros
Copy link
Member

Hello @srh ,
Shouldn't we assign this issue to 2.4.x blockers?

@srh
Copy link
Contributor

srh commented Nov 25, 2019

No, the bug is in 2.3.6.

@gabor-boros
Copy link
Member

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.

@srh
Copy link
Contributor

srh commented Nov 25, 2019

No, it's not fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants