[DOCS-150] Note that aggregate command can be expensive on mongos Created: 01/Mar/12 Updated: 29/Nov/12 Resolved: 19/Mar/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 48 weeks, 2 days ago |
| Description |
|
In a sharded cluster, aggregate can do a lot of work inside the mongos process. Heretofore, mongos has had a modest computational load; aggregate changes that. We need to make this explicit in the docs someplace. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 19/Mar/12 ] | |||||||
|
comment inserted | |||||||
| Comment by auto [ 19/Mar/12 ] | |||||||
|
Author: {u'login': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: | |||||||
| Comment by Richard Kreuter (Inactive) [ 13/Mar/12 ] | |||||||
|
Looks kosher to me. Thanks, Sam. | |||||||
| Comment by Sam Kleinman (Inactive) [ 13/Mar/12 ] | |||||||
|
Richard, Can you review the paragraph in the above comment (or reassign it to Dan P., or someone else) and see if I have the note right and then assign the ticket back to me so I can add it to the manual. Cheers, | |||||||
| Comment by Sam Kleinman (Inactive) [ 05/Mar/12 ] | |||||||
Do you think that the above admonition describes this change appropriately or do you think more description or guidance is required? |