Why does my Node application drop its connection pool to MongoDB Atlas every few hours and how do I configure keep alive settings
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Why does my Node application drop its connection pool to MongoDB Atlas every few hours and how do I configure keep alive settings
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
MongoDB Node.js driver connection pool options maxIdleTimeMS minPoolSize maxPoolSize keepAlive Atlas documentation OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 | |
Mongoose connection options MongoDB Node.js driver heartbeatFrequencyMS serverSelectionTimeoutMS documentation OBSERVED | Google ↗ AI Mode ↗ | — | Comparison | — | — | 1x of 1 |