Sanic raising 503 before timeout period exhausted

[Charles-Hello]

8|sanicgame | 2022-04-06T09:46:43: [2022-04-06 09:46:43 +0000] - (sanic.access)[INFO][192.168.1.50:62892]: POST http://192.168.1.145:8888/robot/wx 503 730

[Charles-Hello]

I don't know, after setting these, it will still report the same error

[Charles-Hello]

sanic 22.3.0 use ASGI

[prryplatypus]

How are you making this request? Using cURL or similar? Can you post the command you're using and a small code snippet that this can be reproduced with?

[Charles-Hello]

@prryplatypus I just traverse the list and send requests to other servers

[Charles-Hello]

When I stay in the task for too long, sanic will automatically explode 503 730 errors

[Charles-Hello]

What is the specific reason? ? Is it my bad asynchronous writing or is it a problem with sanic?

[Charles-Hello]

[Charles-Hello]

I have set the value of RESPONSE_TIMEOUT to 60 according to the error report, but the server will still stop the task. When my await asyncio.sleep(30), the sanic server will not even execute the function below, and the terminal will explode 503 directly. , the error of 730

[Charles-Hello]

Just like this, after five or six seconds, the server will not automatically explode 503 and 730 errors

[prryplatypus]

A couple of things I can notice:

1. Try using aiohttp or httpx instead of requests if you can. requests is blocking, and it makes async pretty much useless 😉.
2. Opening files is also a blocking operation. Instead of doing with open(...) on each request, you might want to load the files once during application startup, save it to app.ctx and then read it from there by using request.app.ctx. Note that this will only work if the file's contents is static/doesn't change.
3. You can run the app by simply doing app.run(...). No need to do asyncio.run(app.run(...)).
4. If sending those requests takes some time, you might want to make use of signals, so that you can respond to the request but keep that task running in the background.

As to why the request is timing out before the amount of time you configure, I am unsure why that could be happening. Maybe one of the other devs can help us out.

In the meantime, would you give those steps above a try and let us know if they work?

Best, @prryplatypus.

[Charles-Hello]

solved. But I changed the asynchronous to not asynchronous and solved it. But it looks weird

[prryplatypus]

Glad to hear! I’ll leave this open so @ahopkins can clarify on the 503 when he’s around :)

[ahopkins]

Is this an issue? Closing. If there is an issue please open and provide me with some copy/pastable code to replicate.