The HTTP 503 Error indidicates the server is busy. It might be due to the fact that the servers are overloaded (high load average).
One of my API is designed to return 503 Error when the cached file is not available. It is designed as the follows:
1 2 3 4 | if (!is_file($file)) { throw_503(); die(); } |
if (!is_file($file)) {
throw_503();
die();
}The $file will be updated periodically e.g. every minute via crontab. When the OS is writing to that file, the is_file will return false because the file is in-use.
One way of solving this is to have multiple caching versions, to avoid the single point of failure. For example, if a file-1 is not available we can check for file-2. These two files should not be updated at the same time.
Another way to resolve this issue is to add a delay check (hacky solution), for example:
1 2 3 4 5 6 7 | if (!is_file($file)) { sleep(1); // delay check. } if (!is_file($file)) { throw_503(); die(); } |
if (!is_file($file)) {
sleep(1); // delay check.
}
if (!is_file($file)) {
throw_503();
die();
}–EOF (The Ultimate Computing & Technology Blog) —
loading...
Last Post: SteemJs Programming: What Happens on the Steem Blockchain in the Last 24 Hours?
Next Post: How to Renew the Free SSL Certificates (Nginx Server)?
