Sonarqube后台任务永远运行 [英] Sonarqube background tasks running forever

问题描述

我们现在已经运行SonarQube 5.6.4了一段时间。然后我们突然观察到后台任务的队列正在增加。在日志中我们看到如下消息：

We have running SonarQube 5.6.4 for a while now. Then we observed suddenly that the queue of background tasks is increasing. In the logs we see messages like that:

2017.07.24 13:56:10 INFO  [o.s.s.es.BulkIndexer] 0 requests processed (0 items/sec)

每分钟一个日志条目。

启动的其他任务失败了：

Other tasks started then are failing with:

org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes were available: [[sonar-1498219166409][3QkGfCI8RUSn6vapRi5SSg][a2d477fdfe7a][inet[/127.0.0.1:9001]

我不知道如何找到导致错误的任何内容。配置中没有任何变化。

I do not know how to find anything which is causing the error. Nothing has changed in the configuration.

我重新启动服务器但没有任何改变。

I restarted the server but nothing changed.

对我来说有什么值得注意的是弹性搜索似乎打开的端口数：

What is remarkable for me is the number of ports which seems to be opened by elastic search:

tcp        0      0 localhost:etlservicemgr localhost:53058         ESTABLISHED 24/java
tcp        0      0 localhost:etlservicemgr localhost:53070         ESTABLISHED 24/java
tcp        0      0 localhost:53058         localhost:etlservicemgr ESTABLISHED 220/java
tcp        0      0 localhost:etlservicemgr localhost:52934         ESTABLISHED 24/java
tcp        0      0 a2d477fdfe7a:49760      sonar-db.netwo:postgres ESTABLISHED 220/java
tcp        0      0 localhost:etlservicemgr localhost:52846         ESTABLISHED 24/java
tcp        0      0 localhost:52924         localhost:etlservicemgr ESTABLISHED 119/java
tcp        0      0 localhost:52928         localhost:etlservicemgr ESTABLISHED 119/java
tcp        0      0 localhost:53076         localhost:etlservicemgr ESTABLISHED 220/java
tcp        0      0 localhost:etlservicemgr localhost:52866         ESTABLISHED 24/java
tcp        0      0 localhost:53074         localhost:etlservicemgr ESTABLISHED 220/java
tcp        0      0 localhost:etlservicemgr localhost:52922         ESTABLISHED 24/java

（实际上是五倍）

有谁知道如何找到问题的原因？

Has anyone an idea how to find the cause of the problem?

sonarqube.properties有默认值。只有以下更改：

sonarqube.properties has default values. Only changes are:

sonar.security.realm=LDAP
sonar.security.savePassword=true
sonar.security.updateUserAttributes=true
sonar.authenticator.downcase=true
sonar.authenticator.createUsers=true

和LDAP配置。

推荐答案

虽然我仍然不明白为什么这些设施被困住了不抛出异常我们的问题似乎可以通过将worker的堆空间从500MB增加到1GB来解决：

While I still not understand why the taks was stuck and did not throw an exception our problem seems to be solved by increasing the heapspace for the worker from 500MB to 1GB:

sonar.ce.javaOpts=-Xmx1024m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true

这篇关于Sonarqube后台任务永远运行的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！