[SERVER-4668] Whats the fix version and which part of the cluster is broken Created: 12/Jan/12  Updated: 02/Aug/18  Resolved: 12/Jan/12

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Aayush Assignee: Unassigned
Resolution: Done Votes: 0
Labels: exception
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows ( 64 bit)


Participants:

 Description   

we are running into this similar issue, and this exception from mongo is causing 500 errors on our Api.
What I want to know is, where exactly is the problem. Upgrading the entire cluster is a more time consuming task.
Is the issue with the router ( mongos ) or is it with the configserver ( mongod ) is it with the latest Java driver?

We want to upgrade the entire cluster, but due to time constraints, I was hoping to get a response about which part of the cluster is broken, and if we upgrade only that, will it solve the problem. Also, it would be great to get a definitive answer about the fix version?
A quick response would be appreciated because its affecting our service.

Thanks.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 12/Jan/12 ]

you should upgrade the whole cluster to 2.0.2

Generated at Thu Feb 08 03:06:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.