Jira 8.9.0在Docker中运行,Cpu使用率高

Jira 8.9.0在Docker中运行,Cpu使用率高,jira,issue-tracking,Jira,Issue Tracking,我的jira实例运行了几个星期,非常正常,但现在它在每次重新启动后运行大约24小时后cpu使用率很高。我已经禁用了所有服务(备份服务、邮件队列服务等),但没有任何帮助 然后我启用了sql日志,并在atlassian-jira-sql.log中找到以下内容: 2020-11-16 18:19:07,067+0000 pool-24-thread-1 0ms "SELECT ID, JOB_ID, START_TIME, RUN_DURATION, RUN_OUTCOME, INF

我的jira实例运行了几个星期,非常正常,但现在它在每次重新启动后运行大约24小时后cpu使用率很高。我已经禁用了所有服务(备份服务、邮件队列服务等),但没有任何帮助

然后我启用了sql日志,并在atlassian-jira-sql.log中找到以下内容:

2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, START_TIME, RUN_DURATION, RUN_OUTCOME, INFO_MESSAGE FROM PUBLIC.rundetails WHERE JOB_ID='com.atlassian.diagnostics.internal.analytics.DailyAlertAnalyticsJob' ORDER BY START_TIME DESC LIMIT 1"
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms Connection returned. borrowed : 0
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms Connection taken. borrowed : 1
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, JOB_RUNNER_KEY, SCHED_TYPE, INTERVAL_MILLIS, FIRST_RUN, CRON_EXPRESSION, TIME_ZONE, NEXT_RUN, VERSION, PARAMETERS FROM PUBLIC.clusteredjob WHERE JOB_RUNNER_KEY='com.atlassian.ratelimiting.internal.history.HistoryCleanupJob'"
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms Connection returned. borrowed : 0
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms Connection taken. borrowed : 1
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, START_TIME, RUN_DURATION, RUN_OUTCOME, INFO_MESSAGE FROM PUBLIC.rundetails WHERE JOB_ID='HistoryCleanupJob' ORDER BY START_TIME DESC LIMIT 1"
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms Connection returned. borrowed : 0
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms Connection taken. borrowed : 1
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, JOB_RUNNER_KEY, SCHED_TYPE, INTERVAL_MILLIS, FIRST_RUN, CRON_EXPRESSION, TIME_ZONE, NEXT_RUN, VERSION, PARAMETERS FROM PUBLIC.clusteredjob WHERE JOB_RUNNER_KEY='com.atlassian.plugins.authentication.impl.web.saml.SamlAssertionValidationService'"
2020-11-16 18:19:07,067+0000 pool-24-thread-1     0ms Connection returned. borrowed : 0
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms Connection taken. borrowed : 1
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, START_TIME, RUN_DURATION, RUN_OUTCOME, INFO_MESSAGE FROM PUBLIC.rundetails WHERE JOB_ID='assertionId-cleanup' ORDER BY START_TIME DESC LIMIT 1"
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms Connection returned. borrowed : 0
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms Connection taken. borrowed : 1
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, JOB_RUNNER_KEY, SCHED_TYPE, INTERVAL_MILLIS, FIRST_RUN, CRON_EXPRESSION, TIME_ZONE, NEXT_RUN, VERSION, PARAMETERS FROM PUBLIC.clusteredjob WHERE JOB_RUNNER_KEY='com.atlassian.plugins.authentication.impl.analytics.StatisticsCollectionService'"
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms Connection returned. borrowed : 0
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms Connection taken. borrowed : 1
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, START_TIME, RUN_DURATION, RUN_OUTCOME, INFO_MESSAGE FROM PUBLIC.rundetails WHERE JOB_ID='analytics-collection' ORDER BY START_TIME DESC LIMIT 1"
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms Connection returned. borrowed : 0
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms Connection taken. borrowed : 1
2020-11-16 18:19:07,068+0000 pool-24-thread-1     0ms "SELECT ID, JOB_ID, JOB_RUNNER_KEY, SCHED_TYPE, INTERVAL_MILLIS, FIRST_RUN, CRON_EXPRESSION, TIME_ZONE, NEXT_RUN, VERSION, PARAMETERS FROM PUBLIC.clusteredjob WHERE JOB_RUNNER_KEY='com.atlassian.audit.retention.RetentionJobRunner'"

这是一个jira实例,只供我使用。日志是在我没有使用jira实例时完成的。 有人知道那里发生了什么吗

或者有人能给jira提供一个替代方案吗?jira也有看板功能