This repository was archived by the owner on Apr 25, 2019. It is now read-only.
This repository was archived by the owner on Apr 25, 2019. It is now read-only.
How to fix the gateway time out issue in an api calling... #77
Description
<--- Last few GCs --->
1186740 ms: Scavenge 1398.0 (1457.4) -> 1398.0 (1457.4) MB, 4.7 / 0 ms (+ 2.8 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
1187878 ms: Mark-sweep 1398.0 (1457.4) -> 1395.8 (1455.4) MB, 1137.7 / 0 ms (+ 124.1 ms in 787 steps since start of marking, biggest step 2.8 ms) [last resort gc].
1189008 ms: Mark-sweep 1395.8 (1455.4) -> 1394.8 (1457.4) MB, 1130.2 / 0 ms [last resort gc].
<--- JS stacktrace --->
- ==== JS stack trace =========================================
Security context: 0x226d302b4629
1: new constructor(aka InternalCache) [/mydata/node_modules/mongoose/lib/internal.js:~10] [pc=0x1329c3a73dcd] (this=0x322f4c825501 <an InternalCache with map 0x62c69cbe239>)
3: constructor(aka Document) [/mydata/node_modules/mongoose/lib/document.js:~39] [pc=0x1329c3be99d8] (this=0x322f4c8255f1 <a model with map 0x62c69...
Can you please help me with this out, How to fix this