You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have got a DB Service that uses mongo, I am using the already existent method "insert". After many calls in a short time I got a REQUEST_TIMEOUT. The issue is, that, finally the insert action is done because I am controlling all the data sent with a simple id, and I can see the json sent saved in the mongo collection.
But, my question is, when the call fails and it is "retryable", which is the method to fire again the call, there is a stack in the memory of the microservice? Is it used the transport? Or is a simple "setTimeOut"? How many retries are done in a REQUEST_TIMEOUT? Why the request_timeout is appear up?
Thank you
RequestTimeoutError: Request is timed out when call 'logs.insert' action on 'e0018-33060' node.
at C:\...\TestingMoleculer\monitor-log\node_modules\moleculer\src\middlewares\timeout.js:42:14
at runMicrotasks (<anonymous>)
at runNextTicks (internal/process/task_queues.js:58:5)
at listOnTimeout (internal/timers.js:523:9)
at processTimers (internal/timers.js:497:7) {
code: 504,
type: 'REQUEST_TIMEOUT',
data: { action: 'logs.insert', nodeID: 'e0018-33060' },
retryable: true
}
The text was updated successfully, but these errors were encountered:
developez
changed the title
I got REQUEST_TIMEOUT makeing many calls againts DB service with mongo. Questions.
I got REQUEST_TIMEOUT making many calls against a DB service with mongo, I have got some questions
Feb 20, 2021
I have got a DB Service that uses mongo, I am using the already existent method "insert". After many calls in a short time I got a REQUEST_TIMEOUT. The issue is, that, finally the insert action is done because I am controlling all the data sent with a simple id, and I can see the json sent saved in the mongo collection.
But, my question is, when the call fails and it is "retryable", which is the method to fire again the call, there is a stack in the memory of the microservice? Is it used the transport? Or is a simple "setTimeOut"? How many retries are done in a REQUEST_TIMEOUT? Why the request_timeout is appear up?
Thank you
The DB Service.
The text was updated successfully, but these errors were encountered: