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

Allow for meridian_server to be restarted #10

Open
wfvining opened this issue May 16, 2016 · 0 comments
Open

Allow for meridian_server to be restarted #10

wfvining opened this issue May 16, 2016 · 0 comments
Assignees
Milestone

Comments

@wfvining
Copy link
Owner

Add a version number (or perhaps a "ref" from erlang:make_ref/0) to the node name in the vector clock. A new ref or version number is created every time the server is restarted, in this way there will be no consistency issues caused by the server's clock restarting from zero --- every time the server is restarted it is considered a new server in the vector clocks of all other servers. NOTE: PIDs cannot be used reliably as a version number as they may be reused in a long running system (I think, although the documentation on this is unclear). Refs won't repeat for 500+ years when created at a rate of 1 per ns, so they should be just fine as version numbers.

@wfvining wfvining added this to the Version 1 milestone May 16, 2016
@wfvining wfvining self-assigned this May 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant