[DOCS-5027] Document configurable idle cursor timeout Created: 16/Mar/15 Updated: 13/Jun/19 Resolved: 16/Jan/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-2.6, mongodb-3.0, mongodb-3.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jon Rangel (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 8 years, 4 weeks, 4 days ago | ||||||||||||||||
| Description |
|
A configurable server-side idle cursor timeout has been added under |
| Comments |
| Comment by Githook User [ 16/Jan/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 16/Jan/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 16/Jan/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Ernesto Valero [ 14/Jan/16 ] |
|
+1 This variable was very usefull for a particular use case of Symphony workbench which it doesn't manage correctly connections agains our mongoDB instance and it doesn't close connections correctly. So I decrease to 5 minutes cursor timeout and our instance wasn't exhausted of connections. Please, add this to the MongoDB docs! |
| Comment by Dave Muysson [ 26/Nov/15 ] |
|
+1!! Our environment uses autoscaling to allow us to grow/shrink based on demand. Unfortunately, on occasion we have run into noTimeout cursors that were opened by hosts which were killed by the autoscaling processes. This has then blocked sharding from migrating data as it was locked by the zombie cursor which can only be cleared by a MongoD process restart. The addition of the adjustable cursor timeout is a very important addition. 10 minutes was not long enough for our environment, which forced us to set noTimeout on our cursors. Since we can adjust it now with this setting (i.e. 30 min/45min), we can move back to standard cursors and stop using the noTimeout flag. Please add this to the MongoDB documentation! This wasn't easy to find, and I'm sure others would benefit from knowing about this addition as well. |