eclipse / jifa

🔬 Online Heap Dump, GC Log, Thread Dump & JFR File Analyzer.
https://eclipse.github.io/jifa/
Eclipse Public License 2.0
541 stars 96 forks source link

Pod Overhead set without corresponding RuntimeClass defined Overhead #269

Closed mark8s closed 8 months ago

mark8s commented 8 months ago

I use the latest code, build the image locally, and deploy it. When analyzing diagnostic files, jifa-master reported the following error:

2024-03-20T02:17:58.477Z  INFO 1 --- [           main] o.s.m.s.b.SimpleBrokerMessageHandler     : Started.
2024-03-20T02:17:58.488Z  INFO 1 --- [           main] org.eclipse.jifa.server.Launcher         : Started Launcher in 7.584 seconds (process running for 8.008)
2024-03-20T02:17:58.491Z  INFO 1 --- [           main] org.eclipse.jifa.server.ReadyListener    : Jifa Server: http://localhost:8102
2024-03-20T02:18:03.779Z  INFO 1 --- [nio-8102-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring DispatcherServlet 'dispatcherServlet'
2024-03-20T02:18:03.780Z  INFO 1 --- [nio-8102-exec-1] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
2024-03-20T02:18:03.782Z  INFO 1 --- [nio-8102-exec-1] o.s.web.servlet.DispatcherServlet        : Completed initialization in 2 ms
2024-03-20T02:18:16.259Z ERROR 1 --- [ker - 1 Starter] o.e.j.s.service.impl.K8SWorkerScheduler  : Failed to start elastic worker, response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"jifa-elastic-worker-1\" is forbidden: pod rejected: Pod Overhead set without corresponding RuntimeClass defined Overhead","reason":"Forbidden","details":{"name":"jifa-elastic-worker-1","kind":"pods"},"code":403}

2024-03-20T02:18:58.293Z  INFO 1 --- [MessageBroker-4] o.s.w.s.c.WebSocketMessageBrokerStats    : WebSocketSession[2 current WS(2)-HttpStream(0)-HttpPoll(0), 3 total, 0 closed abnormally (0 connect failure, 0 send limit, 0 transport error)], stompSubProtocol[processed CONNECT(3)-CONNECTED(3)-DISCONNECT(0)], stompBrokerRelay[null], inboundChannel[pool size = 8, active threads = 0, queued tasks = 0, completed tasks = 36], outboundChannel[pool size = 8, active threads = 0, queued tasks = 0, completed tasks = 12], sockJsScheduler[pool size = 4, active threads = 1, queued tasks = 7, completed tasks = 30]
2024-03-20T02:19:48.201Z ERROR 1 --- [ker - 2 Starter] o.e.j.s.service.impl.K8SWorkerScheduler  : Failed to start elastic worker, response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"jifa-elastic-worker-2\" is forbidden: pod rejected: Pod Overhead set without corresponding RuntimeClass defined Overhead","reason":"Forbidden","details":{"name":"jifa-elastic-worker-2","kind":"pods"},"code":403}

The command to build my image is as follows:

DOCKER_BUILDKIT=1 docker build --build-arg GRADLE_ARGS="clean build -Declipse-mat-deps.os=linux -Declipse-mat-deps.arch=amd64" -f  build.Dockerfile -t jifa-build .

DOCKER_BUILDKIT=1 docker build --build-arg TARGETARCH=amd64 -f  final.Dockerfile -t jifa-release .

image

The container is started normally:

image

Frontend error:

image

D-D-H commented 8 months ago

Sorry. The latest changes haven't been tested well or used by us internally.

One of the changes bumped the k8s client to a new version. Not sure if the problem is caused by that change.

I'll take a look.

D-D-H commented 8 months ago

https://github.com/kubernetes-client/java/issues/3076

D-D-H commented 8 months ago

Please try the latest code or image.

mark8s commented 8 months ago

@D-D-H Okay, I'll get it done in the next few days

mark8s commented 8 months ago

@D-D-H solved