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

Replicaset configuration #124

Closed
jgerry opened this issue Jun 3, 2013 · 4 comments
Closed

Replicaset configuration #124

jgerry opened this issue Jun 3, 2013 · 4 comments

Comments

@jgerry
Copy link

jgerry commented Jun 3, 2013

I'm having some issues configuring a replicaset and had a few questions.

The general problem is this:

  • ruby_block[config_replicaset] action create
    xxx.xxxxx.biz [2013-06-03T19:13:58+00:00] WARN: Cannot configure replicaset 'rep1', no member nodes found

I get this on every node I try to start. Related to the search for other nodes, which don't exist yet? I seem to have the same problem even when I have other nodes up. Is there any way to override the search and just set members via attribute?

EDIT: This is using Chef Server 11 and Chef 11.4.4

@jamesonjlee
Copy link

not at this moment. you issue is probably related to stuff in #118

@tphummel
Copy link

tphummel commented Jul 4, 2013

one option I found to avoid the search() issue with chef-solo is to do:

set['mongodb']['auto_configure']['replicaset'] = false

and do the rs config on the nodes manually

@josephholsten
Copy link

yeah, we really need to support manually setting the replicaset members via node attribute and parameter to mongodb_instance. Technically, your bug is related to search, but I'd rather get a the low-tech hammer working first, then fix the fancy search stuff.

This was referenced Jan 18, 2014
@josephholsten
Copy link

Seems like I'll actually get the fancy stuff first, see #215

@jamesonjlee this seems safe to close

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

No branches or pull requests

4 participants