Hi Pink, > -the users database gets replicated on all nodes? So a single API > call > creates a new user for the entire cluster?
If they're going in the _users database, yes. If you're declaring a server-wide admin that goes in the [admins] section of local.ini, that needs to be done separately on every node. > -configurations need to be done separately on every node? Yes! > Ultimately, as far as configuration goes, I foresee very very few > config > changes. and if I only have 4 nodes, what are the disadvantages to > making 4 > API calls for each change to be made? Or writing a simple script to > iterate > my changes across each node? Only that if you replace a node (due to failure) or grow your cluster, your CM system won't have the built-in support to handle that situation. If you automate handling cluster setup by deploying your local.ini file, you'll be sure to get those settings right across all nodes in the cluster, present *and* future. > I'm > trying > to suss out the dangers of making the calls myself? What can I break? For these changes...nothing. > To be even more blunt... as far as learning a configuration manager > goes... I'm lacking in both gumption and resolve. That just leaves > necessity. Before I assign a higher value to necessity, I'd like to > get a > better understanding of the risks and benefits of each method. Using scripts by hand for now is fine. Later, when you may want to do things like automated deployment, you'll need the power of one of those CM tools. > One last tangentially related question: does the couch per user > setting > work on a cluster? Yes, that's another setting for your local.ini file, so you need to set it on every node separately. -Joan
