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

Delay in startup of the first three machines #7

Closed
neunhoef opened this issue Feb 24, 2017 · 3 comments
Closed

Delay in startup of the first three machines #7

neunhoef opened this issue Feb 24, 2017 · 3 comments

Comments

@neunhoef
Copy link
Collaborator

The starter waits until three machines have registered (including the master) and then starts all processes in quick succession. This creates a race for the names "DBServer0001" and "Coordinator0001". It would be better for users if the starter would delay the startup on machines 2 and 3 slightly, such that the numbering would always be consistent. This is only necessary on the first startup, restarts are fine since the names are taken then.

@ewoutp
Copy link
Contributor

ewoutp commented Feb 27, 2017

Why are the servers picking such "well known" names instead of picking just a random ID?

@neunhoef
Copy link
Collaborator Author

We actually use UUIDs internally. The short names are solely for the purposes of the UI, where we considered the UUIDs to be "ugly". The names "DBServer0001" are also a form of backward compatibility.

@ewoutp
Copy link
Contributor

ewoutp commented Feb 28, 2017

We want to allow renaming the names after creating.
Closing the issue here.

@ewoutp ewoutp closed this as completed Feb 28, 2017
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

2 participants