Kubernetes中的VERTX仅与两个CPU一起使用

发布于 2025-02-03 14:57:21 字数 1830 浏览 1 评论 0原文

我面临着一种非常奇怪的行为，试图垂直扩展，

在我本地计算机中部署时运行多个螺纹，我可以看到多个垂直螺纹和事件 - 环线程是创建的

[] | 2022-06-01 13:29:10.533 [vert.x-eventloop-thread-2] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.534 [vert.x-eventloop-thread-4] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.534 [vert.x-eventloop-thread-3] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.535 [vert.x-eventloop-thread-1] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.535 [vert.x-eventloop-thread-4] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.536 [vert.x-eventloop-thread-7] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.536 [vert.x-eventloop-thread-7] INFO  Async-flow-http-proxy running......

，然后当我运行一些查询时，我可以看到所有事件都可以看到 - 环以向旋转方式使用。

[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-2] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-4] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-6] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-0] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091

但是，当我在kubernetes中部署时，并使用java 11和cpu'10'运行容器。我仍然可以看到创建了多个事件环，但是当我运行请求时，只有两个正在起作用，因此，随着大量流量，我开始只用两个事件循环挣扎

[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-2] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-4] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091

原文

I'm facing a very weird behavior, trying to scale up vertically, running multiple Verticles

When I deploy in my local machine I can see the multiple Verticles and event-loop threads are created

[] | 2022-06-01 13:29:10.533 [vert.x-eventloop-thread-2] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.534 [vert.x-eventloop-thread-4] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.534 [vert.x-eventloop-thread-3] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.535 [vert.x-eventloop-thread-1] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.535 [vert.x-eventloop-thread-4] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.536 [vert.x-eventloop-thread-7] INFO  Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.536 [vert.x-eventloop-thread-7] INFO  Async-flow-http-proxy running......

Then when I run some queries I can see that all event-loops are used in round-robin fashion.

[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-2] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-4] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-6] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-0] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091

But, when I deploy in Kubernetes, and run the container with Java 11, and cpu '10'. I can still see that the multiple event-loops are created, but when I run request, only two of them are working, so then with big traffic I start struggling with only two event-loops

[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-2] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-4] INFO  AsyncFlowHttpProxy - Calling next service localhost on port 8091

分享到QQ

分享到微博