[SERVER-39153] Server not accessible after the error _flushRoutingTableCacheUpdates { forceRoutingTableRefresh: "config.system.sessions" Created: 23/Jan/19 Updated: 30/Aug/19 Resolved: 30/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Valerie FAUTRA | Assignee: | Eric Sedor |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux : el7.x86_64 |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
hi,
|
| Comments |
| Comment by Kelsey Schubert [ 30/Aug/19 ] |
|
Through internal testing, we were able to identify Kind regards, |
| Comment by Eric Sedor [ 20/Mar/19 ] |
|
Hi, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Eric Sedor [ 08/Mar/19 ] |
|
Hi, We still need additional information to diagnose the problem. If this is still an issue for you, can you see if any of the above information is available? Thanks, |
| Comment by Eric Sedor [ 29/Jan/19 ] |
|
Sorry for the added step here. We've been reviewing this ticket again and did notice there may have been an issue related to capped collections. If you're still interested in pursuing this issue, are you able to provide the logs for the affected node during the 2-hour outage? Can you also tell us about how many capped collections you are using, what size they are, and what rate of writes they receive? The diagnostic.data directory and the logs from secondary nodes may also be helpful. I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. |
| Comment by Eric Sedor [ 24/Jan/19 ] |
|
Thank you. This appears to be a performance issue that would require investigation. The log line above is likely a symptom. Because the SERVER project is for reporting bugs or feature suggestions for the MongoDB server, we'd like to ask that you post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. |
| Comment by Valerie FAUTRA [ 24/Jan/19 ] |
|
HI Eric |
| Comment by Eric Sedor [ 23/Jan/19 ] |
|
It is possible for many operations to exceed a maxTimeMS setting when a node is experiencing trouble, but it is not clear from this log message what trouble actually occurred, or if that trouble is the result of a bug. Would you please archive (tar or zip) the $dbpath/diagnostic.data directory from the affected node and attach it to this ticket? |
| Comment by Valerie FAUTRA [ 23/Jan/19 ] |
|
Thanks Envoyé depuis mon smartphone Samsung Galaxy. -------- Message d'origine -------- Sam Rossi a déplacé Projet: Core Server (a été: Mongoid) ---------------------- _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc This message and its attachments may contain confidential or privileged information that may be protected by law; |