[SERVER-4165] Too Many attempts to update config error... Created: 27/Oct/11 Updated: 11/Jul/16 Resolved: 28/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Osterhaus | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Sharded mongod cluster. Consists of 2 shards. Each shard consists of 3 server replica set. we have 2x mongos process running on 2 seperate servers. |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Running a sharded cluster, consisting of 2 shards. We are using 2 mongos processes. MONGO ACCESS PROFILE: We are running 2x mongos processes. I'm seeing errors like the following: ERRORS
|
| Comments |
| Comment by Aayush [ 12/Jan/12 ] |
|
Thanks for the quick response Eliot. |
| Comment by Eliot Horowitz (Inactive) [ 12/Jan/12 ] |
|
I would recommend upgrading the whole cluster to 2.0.2 |
| Comment by Eliot Horowitz (Inactive) [ 12/Jan/12 ] |
|
I would recommend upgrading the whole cluster to 2.0.2 |
| Comment by Aayush [ 12/Jan/12 ] |
|
we are running into this similar issue, and this exception from mongo is causing 500 errors on our Api. 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? Thanks. |
| Comment by Eliot Horowitz (Inactive) [ 28/Oct/11 ] |
|
I think its fixed in 2.6.5 |
| Comment by Matthew Osterhaus [ 28/Oct/11 ] |
|
Looks like the update fixed the errors we were having. Jobs running against mongo today look much better on that front. Looks like we are also seeing some null pointer exceptions like folks were seeing here: You know if this was fixed in 2.6.5? (was a bit unclear to me from the responses in that thread.) Original issue is fixed. Thanks again Eliot! |
| Comment by Eliot Horowitz (Inactive) [ 27/Oct/11 ] |
|
I believe you are seeing |