Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
3
-
Description
Problem Definition
Related to JSWSERVER-15051 and JRASERVER-65602
JIRA will have memory pressure (and may hit OOME) in case user creates board with filter with large number of issues (20k+). This might lead to performance problems at busy instance.
While ticket JRASERVER-65602 focuses on empty filter to prevent simple mistakes, it's possible to create filter with large result set.
Suggested Solution
Create a new application variable BOARD_ISSUES_COUNT_LIMIT (suggested default value 5000), similar to jira.bulk.edit.limit.issue.count in jira-config.properties
While opening any board or changing board filter, check the issues count return by board filter and compare it with BOARD_ISSUES_COUNT_LIMIT.
- Display board only when it has less issues than limit.
- Display warning message if condition fails and redirect users to contact Jira admins.
- see also related JRASERVER-66791
Workaround
None
Attachments
Issue Links
- is related to
-
JSWSERVER-15051 Agile board with empty filter can trigger OOME
- Closed
-
JRASERVER-66791 Make Lucene Search with unlimited PageFilter fail to prevent unnecessary memory allocation
- Gathering Impact
-
JRASERVER-65602 As an JIRA Administrator I want to make empty JQL return no data
- Closed