[SERVER-1544] blocking for replication returns success with no replication configured Created: 02/Aug/10 Updated: 12/Jul/16 Resolved: 02/Aug/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.4.4 |
| Fix Version/s: | 1.5.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nick Leippe | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ubuntu 10.04.1, x86-64 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
> db.printReplicationInfo() > db.printSlaveReplicationInfo() > coll.insert({}) ) { "err" : null, "n" : 0, "ok" : 1 }The above should fail--it could not possibly have replicated to two servers since there is only one. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 13/Aug/10 ] |
|
The case doesn't address the issue you're having at all. |
| Comment by Nick Leippe [ 13/Aug/10 ] |
|
still having some problems with this: in the shell, I get the expected behavior: ) but from with this python code: I still get: File "build/bdist.linux-x86_64/egg/pymongo/database.py", line 294, in command So, for some reason the driver is still raising an exception. |
| Comment by Nick Leippe [ 02/Aug/10 ] |
|
just tested on 1.5.6, same behavior still exists. |