[JAVA-1302] MongoDB Cursor timeout Created: 02/Jul/14 Updated: 11/Sep/19 Resolved: 31/Jul/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API, Query Operations |
| Affects Version/s: | 2.12.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Daniel Heitepriem | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | cursor, exception, java, sharded-cluster, timeout | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB Sharded Cluster with two replica sets |
||
| Description |
|
I'm using an sharded-cluster with a java application. After a specifid time (10 minutes or more) I got the following exception:
Is there a way to disable this timeout of the cursor within the sharded-cluster or within the config-file? Thank you very much, |
| Comments |
| Comment by Jeffrey Yemin [ 31/Jul/14 ] |
|
Thanks for responding with the outcome. I'm going to close this ticket. |
| Comment by Daniel Heitepriem [ 05/Jul/14 ] |
|
Hi Jeff, just as a result. It was indeed a network problem. After implementing a heartbeat the problem was solved. Thank you for your help. |
| Comment by Daniel Heitepriem [ 03/Jul/14 ] |
|
Hi Jeff, Regards, |
| Comment by Jeffrey Yemin [ 02/Jul/14 ] |
|
This isn't a cursor timeout, it's a socket exception. Using Google Translate, it looks like the message is something like "Exceeded connection timeout". The default for the driver is to never time out on socket reads (see com.mongodb.MongoClientOptions#getSocketTimeout). Is your application by any chance changing that default? If not, it's possible that a timeout is being triggered lower down in the stack, and you'll have to do some analysis of your network to find the root cause. |