You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If choosing between two recipes that accomplish the same thing, but one is simpler and the other is more complicated... which is better? I am thinking about the idea that the variable shard_name may be extraneous, and that it complicates usage of this recipe by adding yet another variable which you have to think about and understand. When setting up a shard manually (without chef), do you usually assign shard_name? A shard is either a replica set, or it's a single machine. What makes sense is to name the replica set with a replicaset_name. And just that. Only that. Perhaps I am missing something though.
tl; dr is shard_name really needed?
The text was updated successfully, but these errors were encountered:
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.
Copied from edelight/chef-mongodb#95
If choosing between two recipes that accomplish the same thing, but one is simpler and the other is more complicated... which is better? I am thinking about the idea that the variable shard_name may be extraneous, and that it complicates usage of this recipe by adding yet another variable which you have to think about and understand. When setting up a shard manually (without chef), do you usually assign shard_name? A shard is either a replica set, or it's a single machine. What makes sense is to name the replica set with a replicaset_name. And just that. Only that. Perhaps I am missing something though.
tl; dr is shard_name really needed?
The text was updated successfully, but these errors were encountered: