[SERVER-36271] saslStart { saslStart: 1, mechanism: "SCRAM-SHA-1", payload: "xxx" } numYields:0 reslen: 155 locks:{} protocol:op_query 398387ms Created: 25/Jul/18 Updated: 27/Oct/23 Resolved: 02/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.9 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | shawn | Assignee: | Nick Brewer |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
HI One mongodb instance was killed by oom killer, After starting it, couldn't connect to it by using mongo client. Finding some logs from log: 2018-07-24T19:15:40.241+0800 I COMMAND [conn33] command admin.$cmd command: saslStart { saslStart: 1, mechanism: "SCRAM-SHA-1", payload: "xxx" } numYields:0 reslen:
mongodb server version is 3.4.9 |
| Comments |
| Comment by Nick Brewer [ 02/Aug/18 ] | ||||||
|
From your responses, I do not see anything to indicate a bug in the MongoDB server. For MongoDB-related support discussion please 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. -Nick | ||||||
| Comment by shawn [ 31/Jul/18 ] | ||||||
|
I'm sure , it isn't cause by not having enough available memory. When restart mongod , the memory that mongod used is released to OS. And, when i restart mongod, i won't connect to mongod rapidly still, mongodb monitor have a execption with "i/o timeout".
| ||||||
| Comment by Nick Brewer [ 30/Jul/18 ] | ||||||
|
shawn001 From what you're describing, it seems likely that the server still doesn't have enough available memory when it is brought back up, which is why the attempts to authenticate to it are taking so long, and are ultimately timing out. What does the memory utilization look like when the mongod is brought back up? The output of vmstat 1 10 would be useful. Thanks, | ||||||
| Comment by shawn [ 26/Jul/18 ] | ||||||
|
yes, these logs just after the mongod started. when it start, i connect to it, but the connection was blocked. i found some lock info from pstack: Thread 75 (Thread 0x7fa740b43700 (LWP 191319)):
detail pstack info file was attached as follows.
| ||||||
| Comment by Nick Brewer [ 25/Jul/18 ] | ||||||
|
shawn001 Are these logs from right after the mongod is started? What does the memory availability on the machine look like when this occurs? Thanks, |