|
[
Permlink
| « Hide
]
Paul Curren [Atlassian] added a comment - 28/Nov/07 07:45 PM
This issue was created from http://jira.atlassian.com/browse/CONF-10011
 I manage an instance of Confluence with ~2000 users and about 12,000 hits per day. After disabling the Activity plugin we went from an average system load of 3, with regular spikes to 8 to an average load of .1 with spikes to 1.5.
Version Info: Attached is another sample threadump.
I too am hitting this issue. I have attached threadump.txt.
My environment: 2.6.0 Build:#913, MySQL DB, RedHat linux Major slows just started happening, and it was apparent form the thread-dump that the usage tracking plugin was causing the issue. I disabled the plugin, and it works fine. The plugin version I was using was 0.72. So I just upgraded to usage plugin 0.8 (because 0.9 is not compatible with confluence 2.6), and the plugin is installed, however no data is being collected.... Are we supposed to restart after installing the plugin? The documentation doesn't say anything about this... Does anyone know why no data is being collected after installing the 0.8 version? Anyone experienced this? Sherif Found my problem:
2008-09-11 11:09:50,133 ERROR [http-8080-Processor4] [ext.usage.event.UsageEventListener] handleEvent Error creating task to index for event:com.atlassian.confluence.event.events.content.page.PageViewEvent[source=com.atlassian.confluence.pages.actions.ViewPageAction@bbddbf] : java.lang.NoClassDefFoundError: org/apache/lucene/document/Fieldable
-- url: /display/delivery/Charters | userName: test | action: viewpage | page: 4341013
java.lang.NoClassDefFoundError: org/apache/lucene/document/Fieldable
at com.atlassian.confluence.ext.usage.event.UsageEventListener.handleEvent(UsageEventListener.java:57)
at com.atlassian.event.DefaultEventManager.sendEventTo(DefaultEventManager.java:131)
...
(For all those copy-pasting their errors in Google - hope this helps!) For anyone searching:
We disabled the tracking plugin for the moment until this is fixed. Hi.
We're running a Confluence installation with 16,500 users, 620,000 documents, 60,000 attachments and roughly 200,000 hits a day. I'm doing some performance tuning as the system is getting overloaded I've have discovered issues with the usage stat plugin in our load test rig. I'm currently running 40 concurrent users (20% create page, 20% edit page and 60% view page) with a copy of the production database. The number of DB connections jumps up from 10 to 40 under load. I found that it was the usage plugin that caused this (a thread dump revealed 33 threads locked just as described in this ticket). If I disable the Usage Event Listener in the usage stats plugin, then the problem goes away. I've seen I/O load problems in the live installation (index/plugin/usage), but I've only seen these new performance problems in the load testing system. I think it's because the tuning allows for a higher request throughput, but I won't be able to confirm that until I've run another like-for-like test run of the untuned setup (when the load test controller will be available again). Version 0.9 has the same problems. I hope this information may shed some light on the problems with this plugin. I'll have to analyse the extent of the usage of this plugin and potentially uninstall it as it simply doesn't seem fit for large scale systems. Regards, When I installed this plug-in, it said there was an error during the install. It will not let me uninstall, though I did disable it. Even then, I am pretty sure we had to reboot and take disable it manually to prevent it from crashing the system – you couldn't get into the admin, let alone the repository to disable it.
After our upgrade to 2.8, I thought I'd give it another shot. I enabled it and I went to see what the components were on the Plugins page, (NOT the repository) to see if I could enable/disable the problematic ones, I received a system error when just clicking the link to view the installed plugins. Because the Plugins page remembers the last viewed plugin, it renders that page completely unusable until we reboot, even after the plugin has been disabled through the repository. I still cannot uninstall this plugin, and there is no other version that I can find to try to roll it back to a prior version. I can't reinstall it to overwrite what is already there. Is this a problem with uninstall abilities or with this particular plugin? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Open
Major
Usage tracking plugin cause locking issues and slow down system
