Constant CPU and database activity caused by the "Confluence daily summary email" plugin

[Peter Binney]

After moving to 4.3.2 (from 2.8) we noticed a fairly constant 20-30% CPU activity, when no-one was logged in.

We have had a very long-running ticket (CSP-91472) on this with your Josua Masikome on this.

We discovered that it is caused by the Confluence daily summary email plugin.

Despite having default settings (run once a week) it runs more or less constantly, doing something for each user in cwd_user.

It doesn't even restrict itself to users who have ever logged in. We have ~25,000 cwd_user's but, on this instance only 2 had ever logged in.

Despite that, we saw from a database trace that it is cycling through all 25,000!

Scheduled Jobs shows the Job scheduledjob.desc.summaryEmail running.

Since we can't see any need for the features we understand that this plugin provides we have turned it off.

But, it seems wrong that:

a. it processes for every potential user of the system rather than those who have ever used it

b. it takes so much resource

c. it runs so frequently (it seems to run every hour)

[William Zanchet [Atlassian] · Accepted solution]

Hi Peter,

For this case, it's better to have a deeper investigation on that, because isn't something trivial that we can troubleshoot through Answers, we need to see the logs.

Could you please raise a ticket in the http://support.atlassian.com ?

Cheers,

WZ

[Peter Binney]

Hi William - the problem was discussed at length under https://support.atlassian.com/browse/CSP-92426 (this post was auto-created when I raised that ticket).

We have turned the plugin off. As per many other peoples comments (https://confluence.atlassian.com/display/DOC/Configuring+the+Recommended+Updates+Email+Notification?focusedCommentId=313465943#comment-313465943) we a) do not want Confluence spamming people who have never (and will never) use the wiki and b) don't know what (else) the plugin does.

So, from our POV this issue is now closed.

Many thanks!

[Jeremy Largman]

There is a bug report for this at https://jira.atlassian.com/browse/CONF-30581