Replies: 1 comment 2 replies
-
How are your other endpoints structured? Are they async or blocking? If they're not explicitly async, then they're probably blocking, which would mean that you're probably thread-starved. (High-performance Play idiom is that all entry points should be async unless they're pretty trivial.) NB: I know Scala usage of Play far better than I do Java usage, so there's going to be a limit to how much I can chime in. But from what you're saying, and knowing how Play works, that's what I would look for first. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, we have a Play 2.8.19 application deployed in Docker containers on AWS Elastic Container Service.
During periods of high traffic, containers sometimes report as "unhealthy," causing them to be terminated and replaced. The health check is simply a
GET version
endpoint:According to ECS, the problem is that the
GET version
endpoint times out, never returning a response, three consecutive times in a row.I'm having trouble determining the cause of this issue. Upon reviewing the Play logs, there is no warning or error indicating why the application would become unresponsive. However, this endpoint is so simple that I don't understand where/how it could be timing out unless the entire application has become unresponsive.
A few possibilities I've considered:
Ultimately, I see the symptoms of an issue, but no clear indication as to what the issue is. As a result, I'm curious if anyone in the community with more knowledge might know what the issue could be, or if there's any steps I can take to troubleshoot or get more useful logs to pinpoint the problem.
If it's helpful, a few details about our app:
Beta Was this translation helpful? Give feedback.
All reactions