[DOCS-455] mongorestore manpage improvements Created: 29/Aug/12 Updated: 30/Oct/23 Resolved: 12/Sep/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 25 weeks, 1 day ago | ||||||||
| Description |
|
It needs to explain that mongorestore just does inserts, and will not update existing data. Also, need to mention that it does fire-n-forget inserts, and does not do safe writes. |
| Comments |
| Comment by Githook User [ 22/Aug/17 ] |
|
Author: {'username': 'kay-kim', 'email': 'kay.kim@10gen.com', 'name': 'kay'}Message: |
| Comment by Githook User [ 19/Aug/17 ] |
|
Author: {'username': 'kay-kim', 'email': 'kay.kim@10gen.com', 'name': 'kay'}Message: |
| Comment by Githook User [ 17/Aug/17 ] |
|
Author: {'username': 'kay-kim', 'email': 'kay.kim@10gen.com', 'name': 'kay'}Message: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-13T10:42:27-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-13T10:29:08-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: minor: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-13T10:29:08-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: minor: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-13T10:26:33-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: merge: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-12T14:23:56-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}Message: |
| Comment by auto [ 13/Sep/12 ] |
|
Author: {u'date': u'2012-09-12T14:21:22-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}Message: |
| Comment by Sam Kleinman (Inactive) [ 29/Aug/12 ] |
|
right. just adding note to clarify the aforementioned change in case I'm not the one to work on this ticket. |
| Comment by Scott Hernandez (Inactive) [ 29/Aug/12 ] |
|
As I stated, it does not do plain "safe" writes (w:1) since w<2 is not supported. If you do a w:2 on single replica set member it will hang indefinitely waiting for a second node to acknowledge the replication oplog write. |
| Comment by Sam Kleinman (Inactive) [ 29/Aug/12 ] |
|
--w added in 2.2 adds write concern support. |
| Comment by Scott Hernandez (Inactive) [ 29/Aug/12 ] |
|
Also, w < 2 is ignored. https://github.com/mongodb/mongo/blob/master/src/mongo/tools/restore.cpp#L354 |