文物可以解决掌舵图表
当我需要部署我的应用程序USIGN HELM图表时，我会面临问题： 存储库的更新正计时，我们无法部署。 在我看到的日志中
2-06-14T09:33:53.151Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Virtual Metadata stuck tasks: 4651
2022-06-14T09:33:53.151Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Docker Catalog Index stuck tasks: 23
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Metadata stuck tasks: 2
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Maven Metadata stuck tasks: 243
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Conan Metadata stuck tasks: 272
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Npm Metadata stuck tasks: 1
2022-06-14T09:33:53.313Z [jfrt ] [WARN ] [9da4cfb83d1da2c5] [.r.ArtifactoryResponseBase:174] [tp-nio-8081-exec-159] - Client Closed Request 499: java.io.IOException: Broken pipe
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Virtual Metadata stuck tasks: 4652
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Docker Catalog Index stuck tasks: 23
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Metadata stuck tasks: 2
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Maven Metadata stuck tasks: 243
： 7.38.10 Rev 73810900 重新启动的文物解决了问题，但这确实不便。
知道我如何解决这个问题？
i am facing issue sometime when i need to deploy my apps usign helm charts:
the update of repository is getting timed out and we can't deploy.
in the logs i see:
2-06-14T09:33:53.151Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Virtual Metadata stuck tasks: 4651
2022-06-14T09:33:53.151Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Docker Catalog Index stuck tasks: 23
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Metadata stuck tasks: 2
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Maven Metadata stuck tasks: 243
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Conan Metadata stuck tasks: 272
2022-06-14T09:33:53.152Z [jfrt ] [INFO ] [185bdda5673ce024] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Npm Metadata stuck tasks: 1
2022-06-14T09:33:53.313Z [jfrt ] [WARN ] [9da4cfb83d1da2c5] [.r.ArtifactoryResponseBase:174] [tp-nio-8081-exec-159] - Client Closed Request 499: java.io.IOException: Broken pipe
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Virtual Metadata stuck tasks: 4652
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Docker Catalog Index stuck tasks: 23
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Helm Metadata stuck tasks: 2
2022-06-14T09:33:58.153Z [jfrt ] [INFO ] [d095d20ce78b7e4b] [.AsyncWorkQueueServiceImpl:275] [WorkQueueJob ] - Executing Maven Metadata stuck tasks: 243
Version used: 7.38.10 rev 73810900
A restart of Artifactory fixes the issue however this is really inconvenient.
Any idea how I can fix this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
检查在托管文物的主机上是否有任何内存或CPU密集过程正在运行。我在伪影7.37.xx版本上也有同样的问题，我发现我们的一个文物复制过程之一是使用了很多资源，这些资源导致这些陷入困境的消息，在赫尔姆索引上，inturn导致Helm Repo添加和更新，主要是失败，并且在此by。舵机安装。
Check if there are any memory or cpu intensive process are running on the host where the artifactory is hosted. I have the same problem with Artifactory 7.37.xx version and I found that one of our artifactory replication process was using a lot of resources which lead to these stuck messages on helm indexes, inturn causing helm repo add and update to mostly fail and there by helm install.