SonarQube Background task halts silently if component count is to high

[roman.w...@googlemail.com]

I'm currently having issues with the Background Task that process the Data which is sent by a Jenkins server.
As far as i can tell this seems to be some sort of deadlock that occurs as soon there is a high amount of separate components.

I´ve tested a simple Setup that uses the same structure and it does not fail. As soon as i add all components the background task fails.

simple sonar-project.properties:
http://paste.ubuntu.com/14876339/

failing sonar-project.properties:
http://paste.ubuntu.com/14876346/

the last line of log in the failing analysis is always:

2016.02.03 17:34:48 INFO  [o.s.s.c.s.ComputationStepExecutor] Enable snapshot | time=765ms

in the simple example the Logs show following behaviour:
2016.02.03 16:59:05 INFO  [o.s.s.c.s.ComputationStepExecutor] Enable snapshot | time=454ms
2016.02.03 16:59:06 INFO  [o.s.s.c.s.ComputationStepExecutor] Index components | time=125ms
2016.02.03 17:01:19 INFO  [o.s.s.c.s.ComputationStepExecutor] Purge db | time=133606ms
2016.02.03 17:01:19 INFO  [o.s.s.c.s.ComputationStepExecutor] Apply permissions | time=0ms
2016.02.03 17:02:21 INFO  [o.s.s.es.BulkIndexer] 61864 requests processed (1031 items/sec)
2016.02.03 17:02:42 INFO  [o.s.s.c.s.ComputationStepExecutor] Index issues | time=83186ms
2016.02.03 17:02:43 INFO  [o.s.s.c.s.ComputationStepExecutor] Index tests | time=110ms
2016.02.03 17:02:43 INFO  [o.s.s.c.s.ComputationStepExecutor] Send issue notifications | time=0ms
2016.02.03 17:02:43 INFO  [o.s.s.c.s.ComputationStepExecutor] Publish task results | time=0ms
2016.02.03 17:02:43 INFO  [o.s.s.c.t.CeWorkerCallableImpl] Executed task | project=test | id=AVKn2BQ27r87X7KxZ4eM | time=459085ms

thus there seems to be some sort of deadlock or extremely inefficient part in the "Index Components" or "Purge db" Tasks.
Also if the failing background task surpasses the "Enable snapshot" the System load drops to idle.
For testing purposes i also let one Background Task runt for several days but it didn't proceed beyond the "Enable Snapshot" point.

i might be noteworthy that right now using the Evaluation Database and tested this issue with Sonarqube 5.2 and 5.3

I'm not quite sure if i just handling my properties file wrong or if this is an issue. So it would be nice if i´d get some feedback.

Greetings
Roman

[Fabrice Bellingard]

Hi Roman,

first of all, don't expect production-level performances if you're running SQ on the embedded H2 database. This is why we clearly display the red banner at the bottom of the pages in order to warn you about this.

Second, I have the feeling that you are trying to do something wrong: writing a sonar-project.properties file just to analyse all your projects at the same time. I have this feeling because the "modules" that you define in this file all point to different folders at the root of the "D:" drive. So looks like these are different projects that should be analysed independently (but I might be wrong). Can you confirm?

Best regards,

Fabrice BELLINGARD | SonarSource SonarQube Platform Product Manager http://sonarsource.com

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/85c88bb2-362a-4780-8d8e-962823a9aaea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[roman.w...@googlemail.com]

Thank you for the quick response.
I guess i'll try to use a external database. Though the "Project" contains our whole backend. Currently we dont really have well-defined Projects thats why i used one SonarQube project to analyse the whole Backend. I'll send an update as soon i tried the same case with a external database.