Closed AlbertMitjans closed 1 year ago
This is probably an error thrown by nginx to avoid DDoS attacks. There three facts that support this hypothesis: 1- Time needed for the error to appear is not the same between executions.
Assuming we are pointing to the right the direction, this is an evidence of lack of scalability of our current system, although we can probably modify nginx configuration to avoid that. How urgent is this issue? We don't think it is critical by now since the rest of the users aren't using while loops, probably.
I was running the following code:
And got the following output:
Any idea what might be happening?