Showing 2 different project count in 2 different screens


(Mahesh Rajannan) #1

All the help is appreciated.

  • versions used : Sonarqube Enterprise 7.5 (trying out)
  • steps to reproduce
  1. Imported data from S.Q 7.2.1 C.E schema to a schema again used by another instance of SQ 7.2.1.
    2.Then upgraded the instance, with migrated data to SQ 7.3 Enterprise.
  2. Then upgraded the instance , with migrated data to SQ 7.4 enterprise.
  3. Then upraded the instance, with migrated data to SQ 7.5 enterprise.

At this point the home screen (/projects?sort=-analysis_date) in SQ 7.5 enterprise shows 704 projects…instead of 1591 projects.
But the /admin/projects_management screen shows 1591 projects correctly…

We did not use the SQ dB migration tool as we are under trial and do NOT have enterprise license.

Does this indicate some broken foreign keys some how ??

  • potential workaround


  • errror observed (wrap logs/code around triple quote ``` for proper formatting)


(Simon Brandhof) #2

In the first screen, are you authenticated with the same administrator account? Can you send the System Info report please? (Administration > System > Download System Info)

(Mahesh Rajannan) #3

I will check if i can send the System info.

All the projects seem to exist in both the places. The problem is that some how the links are broken and NOT able to search it…Is it do with ES temp cache ?

A project detail shows up when i go directly to the url --> /dashboard?id=hello-world-gradle%3Ascm-org

But the same does not show up when i search by search bar in the top right corner with project key "hello-world-gradle:scm-org



(Simon Brandhof) #4

That does not relate to your initial post. Search engine does not support typing a word longer than 15 characters, except if it matches the project key. You should try with “hello” only.

(Mahesh Rajannan) #5

I know this leading the root cause to be in a different direction.
To me, the issue is that the search and the home page , do not search the full available data…resulting in inconsistent count.

Then i see this error printed in the es.log many times.

2019.03.27 08:55:02 INFO es[o.e.c.r.a.DiskThresholdMonitor] low disk watermark [85%] exceeded on [gYFWNh3WRGyyo6c9on3TbA][sonarqube][/opt/sonar/sonarqube-7.5-d-sonar-2/data/es5/nodes/0] free: 1.8gb[13.8%], replicas will not be assigned to this node


(Simon Brandhof) #6

Can you try to delete the directory data/ and restart the server please? That will re-index data, including projects.

(Mahesh Rajannan) #7

Done. Is there a way to,

  1. Increase the Embedded ES-application limits to 90% ?
  2. Increase the disk allotted to SQ and ES…?
2019.03.27 11:12:54 INFO  es[][o.e.i.IndexingMemoryController] stop throttling indexing for shard [[components][1]]
2019.03.27 11:13:00 INFO  es[][o.e.c.r.a.DiskThresholdMonitor] low disk watermark [85%] exceeded on [oeO0r1WSR--ycjEqKf7YIA][sonarqube][/opt/sonar/sonarqube-7.5-d-sonar-2/data/es5/nodes/0] free: 1.6gb[12.4%], replicas will not be assigned to this node
2019.03.27 11:13:05 INFO  es[][o.e.i.IndexingMemoryController] now throttling indexing for shard [[components][3]]: segment writing can't keep up```

(G Ann Campbell) #8


Ideally in a production instance you’re going to store the ES data in a different volume. See the ‘Configuring the Elasticsearch storage page’ section in the docs.