- From: Brad Knowles <
- Cc: Brad Knowles <
- Subject: [chef] Re: Re: Re: New Community Cookbook: MongoDB
- Date: Fri, 16 Sep 2011 09:30:40 -0500
On Sep 16, 2011, at 1:13 AM, markus korn wrote:
> first of all, thanks for using the mongodb cookbook, and your feedback.
Thank you for all the hard work you've put into this cookbook! There are
other cookbooks for MongoDB that we've seen, and while they are simpler and
easier to use, they are ... simpler -- they don't do sharding, they don't do
replicasets, etc.... You've clearly done a lot of hard work here.
We're just trying to figure out how to adapt this to also work on CentOS 5.6,
and sometimes we get tripped up by being less than completely familiar with
Chef and we don't necessarily recognize when something is an Ubuntu-ism
that's in the cookbook, an Ubuntu-ism that's in Chef, or maybe just our lack
of fully understanding how things work.
> * node['mongodb']['cluster_name'] is defined and has the same value
> for all the nodes in the replicaset (e.g you have one role which
> defines this attribute in 'default_attributes' and this role is in
> every nodes run_list)
Right now, we're trying to get the first node spun up. Once we can get a
machine running under Chef with an empty MongoDB starting up properly (ready
for replicas and shards), then we were planning on tearing it down and firing
up a group of four nodes in a two-shard/one-replicaset-per-shard
configuration and seeing how that works.
I can confirm that on the one node we've been working on so far, this value
is defined and is what we had configured it to be.
> * in every replicaset member there is either directly or indeirectly
> the 'mongodb::replicaset' recipe in the run_list (maybe by also adding
> this recipe to the role )
I'm not seeing this in the run_list at the point where we display that
information, but I don't know if that's being added at a later time. I will
take a look.
> * If you are only using a replicaset (without sharding) you should
> not really care about mongodb's shard_name attribute, it should be set
> to '_default' on all mongodb related nodes
We're not sharded yet, but our production database will be, so we want to
plan for that from the beginning.
> * and last but not least you could check if chef_envionment is set
It seems to be set to "_default", but I don't know if that's correct.
> If I had to debug this further I would remove the the various AND
> conditions from the search statement one-by-one and see if rs_nodes
> has somemembers then. This way it is easy to find the
I'll start decomposing that next.
> I hope I could help you with my hints, please come back if you need
> some more help with the mongodb cookbook.
Indeed, this has been helpful. I will let you know what I find out. Thanks
Archive powered by MHonArc 2.6.16.