[DOCS-3456] mongodb tools and clients in sharded environment for 2.6 need to be updated to new bulk write operations to avoid performance degradation Created: 22/May/14 Updated: 16/Mar/15 Resolved: 24/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 28 weeks ago | ||||||||
| Description |
|
We currently advise customers that mongodb tools that do bulk ingestion using fire&forget with occasional getLastError need to be updated to use the new bulk api to avoid a performance degradation. Client applications coded in a similar manner using any driver (not just mongodb tools) in a sharded environment will see a similar performance degradation until they update the app to use the new bulk write operations, but I don't think we advise customers of that. See |
| Comments |
| Comment by Githook User [ 06/Aug/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |