Unable to limit data for the plugin

[Nikolay Vinogradov]

We have 300k+ issue JIRA instance with several dozen of projects and ~500 users.

At some point someone created a timesheet gadget that accessed following URL: <JIRA_BASE_URL>/rest/timesheet-gadget/1.0/timesheet.json?baseUrl=<JIRA_BASE_URL>&gadgetTitle=My+time+track&startDate=&targetUser=&targetGroup=&collapseFieldGroups=false&excludeTargetGroup=&numOfWeeks=1&reportingDay=2&projectOrFilter=&projectid=11180|10781|10170|10080|11982|10340|10070|13682|13681|10051|13580|13181|10580|13680|10780|10360|12281|10191|10184|10041|10300|10120|11281|10290|10180|11583|10031|10240|10020|11282|12480|10192|10188|10185|10189|10187|10181|10190|10182|12984|13280|11082|13284|10000|13380|11880&filterid=&projectRoleId=&weekends=true&showDetails=true&sumSubTasks=true&showEmptyRows=true&groupByField=&moreFields=&offset=0&monthView=false&sum=

After several retries from Dashboard's AJAX, JIRA stopped responding completely. Worklog limit in the plugin settings was set to 5000. CPU usage at that time was 700+% (it ate 7 cores out of 8 in the system).

In sandbox we have 16 cores and 6G RAM. Running this query ended up with:

Our question(s) are: - how to scale this plugin to our JIRA size correctly? - if it is not possible, then how to prevent users from building such queries? (We're not going to split them into classes: ones who able to see timetracking and ones who don't, because even ones who able could break JIRA in the same way)

[Andriy Zhdanov]

Hi,

Well, such case does not look heavy, it's rather basic and should work normally, I'm surprised it takes 700% CPU. I can only suggest to try if unselecting projects will have any difference, but it should not. There must be something else that causing OOM.

Is it working better if accessing Time Sheet Report?

Thank you.

[Nikolay Vinogradov]

Hi,

No, same thing. Sandbox crashes with out of space, high CPU usage before that.

[Nikolay Vinogradov]

May high CPU usage be caused by ParallelGC threads (8) in JAVA?

[Nikolay Vinogradov]

And i still think that the load is pretty heavy, because it selects many big projects and showEmptyRows=true.

[Andriy Zhdanov]

Ah, sorry, I did not notice showEmptyRows. Yes, with many selected projects it may cause the problem, I will add preventive check for this. But with no projects selected it should not cause a problem. Is it?

[Nikolay Vinogradov]

I think everything is fine without it. But we liked this option for small queries and it should be ok to use it so.

Please help :)

[Andriy Zhdanov]

Right, I will add something similar to Worklog limit.

[Nikolay Vinogradov]

Do you have ETA for the fix?

[Andriy Zhdanov]

This week hopefully.

[Nikolay Vinogradov]

Thanks, waiting for the fix. Meanwhile, downgraded.

[Andriy Zhdanov]

fix issue#811: do not add too many emptyissues

→ <<cset c92206ef7226>>

[Andriy Zhdanov]

Hi,

Version 2.9.5.3 is released with the fix. Please give it a try if it helps.

Thank you.