[DOCS-4164] Cursor do not keep alive in a sharded queries Created: 10/Oct/14  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Ricardo Lorenzo Assignee: Unassigned
Resolution: Won't Fix Votes: 3
Labels: bite-sized, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-6036 Disable cursor timeout for cursors th... Closed
is related to SERVER-8188 Configurable idle cursor timeout Closed
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

When a cursor is active on mongos but the query only reads from a subset of shards, the cursor will time out if the query read again from one of the not used shard members. The feature request for a cursor keepalive in a sharded queries is tracked by SERVER-6036.

It is important to warn the users about this fact to avoid wrong and expensive application design mistakes.



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:47:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.