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
We discovered that if the server runs on AWS for a few days it may get killed due to failing autoscaling health checks. When we disabled the health checks we noticed that the instance would be unresponsive, failing EC2 status checks and sshing to it times out.
Work is in progress to fix this.
The text was updated successfully, but these errors were encountered:
Any updates on the progress/timeline for the fix? The context offered here seems rather concerning to us so any additional information would be helpful. Thank you.
We think it is an out of memory issue due to the continuously ingested test data in that environment. memory consumption in TEE is a bit tricky so we're still in the process of getting concrete evidence.
It turns out that we set Envoy logging verbosity level to DEBUG which generated too much logs and it used up our test machine disk over time. It is unrelated to the server code itself. The verbosity level is fixed.
We discovered that if the server runs on AWS for a few days it may get killed due to failing autoscaling health checks. When we disabled the health checks we noticed that the instance would be unresponsive, failing EC2 status checks and sshing to it times out.
Work is in progress to fix this.
The text was updated successfully, but these errors were encountered: