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

Replication factor #9

Open
madshargreave opened this issue Nov 23, 2018 · 8 comments · May be fixed by #81
Open

Replication factor #9

madshargreave opened this issue Nov 23, 2018 · 8 comments · May be fixed by #81
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@madshargreave
Copy link

Would it be possible to add a replication factor? Ie. only replicate this table on N nodes in the entire cluseter

@beardedeagle
Copy link
Owner

Like at random or do you want to control where they land?

@beardedeagle beardedeagle added the question Further information is requested label Nov 24, 2018
@beardedeagle
Copy link
Owner

I am thinking of these two scenarios:

  • I want this table to only exist in N nodes
  • I want this table to only exist on these specific nodes

And I think I have an idea of how to implement both in one go.

@beardedeagle beardedeagle added enhancement New feature or request good first issue Good for newcomers labels Feb 14, 2019
@madshargreave
Copy link
Author

Exactly the above :)

@beardedeagle beardedeagle removed the question Further information is requested label Feb 21, 2019
@beardedeagle
Copy link
Owner

@madshargreave I've been thinking about this some more and I'm unsure if I want this table to only exist on these specific nodes is a concern of the library. I say this for a couple of reasons:

  • If you are using something like libcluster, then you should be making use of it's whitelist and blacklist capabilities
  • If you are manually managing membership then you have control of this anyway.

Now I could still be convinced of this if the usecase makes sense, but as of the moment I don't think it's a concern of Mnesiac.

I want this table to only exist in N nodes has some use, though this type of check would only happen at startup.

@beardedeagle
Copy link
Owner

I've begun work on this in the replication_factor branch for at least a partial implementation of this request.

@beardedeagle beardedeagle self-assigned this Feb 26, 2019
@beardedeagle
Copy link
Owner

as a heads up, @astutecat suggested also adding a 3rd option for replicating by percentage, so:

  • I want this table to only exist in N nodes
  • I want this table to only exist on these specific nodes
  • I want this table to exist on N% of nodes

@beardedeagle
Copy link
Owner

Sorry, I've been away for some time. I'm getting back to this. Apologies for the inconvenience.

@beardedeagle beardedeagle linked a pull request Aug 2, 2021 that will close this issue
5 tasks
@beardedeagle beardedeagle linked a pull request Aug 2, 2021 that will close this issue
5 tasks
@beardedeagle
Copy link
Owner

I'm hoping to have #53, which this is part of by EOY

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants