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
Do not hang request forever when metadata backend is not able to deliver requests. It's preferable, response with an error before pushing the process to its limits. A symptom of these issues is when Tiler drops a bunch of log entries as follows:
The more entries like this in logs, the worse is performing metadata backend. It makes the customer's request remaining hung in Tiler, memory grows, and GC enters for a long time turning the process unresponsive, and monit triggers a restart of the service, dropping incoming requests.
The text was updated successfully, but these errors were encountered:
Do not hang request forever when metadata backend is not able to deliver requests. It's preferable, response with an error before pushing the process to its limits. A symptom of these issues is when Tiler drops a bunch of log entries as follows:
The more entries like this in logs, the worse is performing metadata backend. It makes the customer's request remaining hung in Tiler, memory grows, and GC enters for a long time turning the process unresponsive, and
monit
triggers a restart of the service, dropping incoming requests.The text was updated successfully, but these errors were encountered: