Artifactory无法解析舵机图表

Question

当我需要部署我的应用程序时，我会遇到一些问题:存储库的更新被超时了，我们无法部署。我在日志中看到：

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重启修复了这个问题，但是这真的很不方便。

知道我怎么能解决这个问题吗？

Answer 1

检查工件所在的主机上是否有任何内存或cpu密集型进程正在运行。我在Artifactory 7.37.xx版本上也有同样的问题，我发现我们的工件复制过程之一是使用大量资源，这些资源导致helm索引上的这些被卡住的消息，从而导致helm添加和更新到大部分失败，并通过helm安装。