[SERVER-3840] Inconsistent handling of arbiters with tags between rs.initiate() and rs.reconfig() Created: 14/Sep/11 Updated: 11/Jul/16 Resolved: 16/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Nick Miller | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 5.4 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
When using rs.initiate with a configuration object that contains an arbiter which has had a tag, configuration is saved successfully and replica set comes online. When reconfiguring using rs.reconfig the following error is generated: { The behaviour is inconsistent. Here is an example configuration session (note host / shard names changed): > cfg = { , , , , , > rs.initiate(cfg); > rs.reconfig(cfg, { force: true}); |
| Comments |
| Comment by auto [ 16/Sep/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: check for tags on arbiter whenever a config is parsed |
| Comment by Nick Miller [ 14/Sep/11 ] |
|
I am assuming that as tags serve no purpose on arbiters, rs.initiate should also return the assertion that rs.reconfig produces. |