|
When are we going to see a fix for this if its not done yet?
And will we see another 1.4 point release for this or am I going to have to risk even more new features on our production systems in order to get the bug fixes? Hi Eric,
I have re-opened this because, JIRA's cache will expire on a periodic basis which may cause serious performance hits until the cache has been rebuilt. I think we still have some investigation to do with regard to smarter cache updating. Unfortunately, I cannot provide an estimated fix version for this at this time. I'm hoping to discuss this with the dev team next week to see where we can fit this in the road map or, perhaps, if I should raise a new, more specific issue for this. I know you experienced some issues with JIRA integration and Crowd's nested-groups capability in the 1.4 release, which we were able to resolve. I completely understand your hesitancy to upgrade to a new major release as a result of this. Please know the team is working hard to provide a smooth 1.5 release. Cheers, I seriously hope you are going to change something in the next release.
Since we have used the crowd-ehcache.xml We have JIRA 3.12.3, Crowd 1.4 and Confluence 2.8.2
Our performance is great, we have over 4000 users. We upgraded recently. We forgot to put the new crowd client libraries in Confluence and Jira and it was still slow, but once we did that it was much better. I don't know why our experience was different.
We're working on this as the top priority for Crowd 1.6. We're still in the investigation phase, so I can't tell you exactly what form the solution will take. But one will come We also still get a bit of a hit, even with the new crowd libs. It's not awful, but if you happen to be using JIRA when the cache expires, it's a bit of a wait. FYI, we have ~8000 users.
I know the design of JIRA necessitates having a copy of all the user data all the time, so I'm not sure what direction you'll need to go. My (unsolicited) suggestion would be to somehow anticipate a cache expiry and have the client update the cache in the background, before the cache actually expires. g. The application cache causes delay between JIRA and Crowd which is really inconvenient. It is glad to see that you've put it as the top priority for Crowd 1.6. We'd like to know when is Crowd 1.6 going to be released? Is there any plan for it yet?
Thanks very much. We're planning to have Crowd 1.6 out before Christmas.
Hi folks,
Crowd 1.6 is now available at the Crowd Download Centre I'm going to close this issue. If, after upgrading to 1.6, you're still experiencing problems, please either contact support Regards, ps: Merry Christmas David,
is the event-based caching mechanism planned or investigated also for OpenLDAP? I can see from the following quote
Cheers, Hi Aggelos,
We're planning on investigating it for OpenLDAP, but we don't have a specific timeframe. Please feel free to create an issue for it. Unfortunately, sync replication and persistent search are different mechanisms, and it appears that OpenLDAP doesn't expose the Persistent Search control. Although, since there are so many ways to configure OpenLDAP, it's possible that we simply haven't managed to set one of our test instances up to correctly expose it. Cheers, |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Setup
Reloading the User Cache
Your results will vary depending on your configuration, the size of your directory instance, and on how fast it is.