Serverless on Active State behaviour
Some APIs I was using on serverless were working on active and idle state before, now it seems to break the server when I switch to active, the response is always the same as the one before, or only finished.
I want to debug what is happening, can someone explain how the state work internally on the handler after it's awake?
What will stay in memory?
Will it run the entrypoint.sh only once correct?
Will it send only start signal once or for every task?:
runpod.serverless.start({
"handler": handler
})
I want to debug what is happening, can someone explain how the state work internally on the handler after it's awake?
What will stay in memory?
Will it run the entrypoint.sh only once correct?
Will it send only start signal once or for every task?:
runpod.serverless.start({
"handler": handler
})
