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 local cluster crashing from non-unique (all the same) generated instance names #5643
Comments
Same result when I try to connect via Python driver. |
@dalanmiller -- is this in the released version? It looks like the last two people to touch the file were @nighelles and @danielmewes . |
Yup, straight from Looks like they are all getting the same name? They all have this line:
|
Yeah, changing the names to be different for each server should be a temporary workaround. I'm looking into fixing this. |
Same error when renaming and retagging all members:
|
Identified that all names being generated for the Work-around: Remove data directory (or else originally generated name will be used) and specify |
The fix for the crash with duplicate names is in review 3595, implemented in nighelles/5643. |
The crash is fixed in next. |
@nighelles Can you backport the fix to the |
(re-opened for backporting) |
This is in 2.3.x |
Creating three node local cluster, rethinkdb (2.3.0 from Homebrew) will run fine until connected to from WebGUI, in this case on
localhost:8083
.The text was updated successfully, but these errors were encountered: