When running Clean Journal Entries, Confluence Page Create, edit cannot be done. and then 502 proxy

유

We are currently using Confluence DataCenter version. (6.8.0) 
At 2am Every day, Clean Journal Entries is operating. 
During the operation of the job, 502 proxy error occurs when accessing the page, Create, Edit, and Confluence. 
When the job is completed, Confluence works normally again.

It takes about 20 to 25 minutes to check the duration of the job. 
Can't you create and edit Confluence's page while the job works?

What will happen if you turn off the job scheduling?

Ross McCoy

Hello,

The "Clean Journal Entries" scheduled job (formerly known as "Optimise Indexing") is very demanding on system resources according to some fairly ancient documentation. However, if you turn off the job scheduling, the size of the journal entries (which are one of the ways that search indexes for nodes in Data Center stay in sync) can potentially grow indefinitely in size, causing you to run out of disk space.

Unfortunately, there's really no public documentation available except the above on precisely what occurs during this job, and I'm not sure how much of the documentation on "Optimise Indexing" applies to "Clean Journal Entries". However, if you have a large Confluence instance, with 3 or more nodes, I would expect some significant performance degradation while this job is occurring based on my experience and the little information I can find online.

If you go to Scheduled Jobs in the Confluence General Configuration, you can see the time (in milliseconds) that it takes to complete the Clean Journal Entries job. What's the time listed here?

If the time listed doesn't match up with what you're expecting to see (1000000 to 1500000 milliseconds) then this job may not be the source of the performance hit you're seeing - by default, Confluence is scheduled to run a backup at 2 AM as well.

You can try modifying the cron expression for this job to run on a weekend, but you will need to closely monitor disk space, especially if you're operating within tight constraints.