PlayFramework并行使用高负载REST API调用
我有一个播放框架的微服务，让我们称其为“服务”（如果很重要，请在kubernetes上运行），并且在集群中还有另一个微服务，将服务称为API Allot，在某些时候，服务器服务Pods崩溃和LIVISE准备就绪也随着超时而失败，但是当我禁用创建请求的服务时，服务再次变得稳定。
我试图理解原因不应该在框中处理负载，还是我需要配置一些东西？
我认为有一个拉动，如果有更多的电话，它将仅阻止它们...因为创建呼叫的服务已重试，可以阻止它。
因此，我的意思是我试图了解是否需要以某种方式为高负载配置可能的游戏或来自其他地方的问题。
思想也许在通话过程中抛出了例外，但是在API呼叫处理过程中某种故障的日志中没有任何例外。
如果您有一个主意，请帮忙，谢谢！
I have a play-framework micro-service lets call it service A (runs on Kubernetes if it matters), and there is another micro-service in the cluster that calls service A api ALLOT, and at some point service A pods crash and liveness readiness also fail with timeout, but when I disable the service who create the requests, service A become stable again.
im trying to understand cause isn't play supposed to handle the load out of the box or I need to configure something?
I thought there is a pull and if there is more calls it will just block them...cause service who creates the call have retries and its ok to be blocked.
so my point is im trying to understand if its possible play need to be configured for high load somehow or the problem coming from somewhere else.
thought maybe there is exception thrown during the calls but nothing in the logs of some sort of failure during the api call processing.
please help if you have an idea, thanks!!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论