-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
7.2.6, 7.2.8
-
None
-
7.02
-
Severity 3 - Minor
-
Description
During the integrity checking procedure, JIRA fired the following query to the database:
SELECT ID, pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT FROM jiraissue
and load the data in the memory. For a large JIRA instance (more than 50 000 issues), loading such amount of data required a big chunk of heap that might cause the memory congestion or garbage collection performance issue.
Suggestion
The result set should paged to limit the size of data to be loaded in the memory to avoid the any memory pressure.
- duplicates
-
JRASERVER-65265 IntegrityChecker may cause intensive JVM memory pressure and FullGC
- In Progress
- mentioned in
-
Page Loading...