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

Cap auto-created retention policy replica count at 3 #3639

Merged
merged 2 commits into from
Aug 12, 2015
Merged

Conversation

jwilder
Copy link
Contributor

@jwilder jwilder commented Aug 12, 2015

Defaulting to the number of nodes in the cluster is doesn't make
sense with larger clusters. (e.g. 10 nodes = RF 10)

@@ -868,6 +868,10 @@ func (s *Store) CreateDatabase(name string) (*DatabaseInfo, error) {
return nil, fmt.Errorf("read: %s", err)
}

if nodeN > 3 {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be clear, we're only supporting 3 node clusters right now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. This is the auto-created retention policy. It just caps the replication factor at 3 instead of using the number of nodes. You can manually create replication factors greater than 3 now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, OK, cool.

Not a huge fan of the magic number. Can you lift it up to MaxAutocreateRPFactor or something?

@otoolep
Copy link
Contributor

otoolep commented Aug 12, 2015

+1 on green build.

Defaulting to the number of nodes in the cluster is doesn't make
sense with larger clusters. (e.g. 10 nodes = RF 10)
jwilder added a commit that referenced this pull request Aug 12, 2015
Cap auto-created retention policy replica count at 3
@jwilder jwilder merged commit 4c7f07b into master Aug 12, 2015
@jwilder jwilder deleted the jw-fixes branch August 12, 2015 20:28
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

Successfully merging this pull request may close these issues.

2 participants