So we rely heavily on Crowd's LDAP caching since our employee directory is just shy of 40,000 employees.
We re-sync every 24 hours to correspond to HR changes. The trouble is that according to my experience and documentation you can only schedule the intenrval, and not the actual time.
This means that if I start a sync now, at 12:00pm (noon) it will re-sync every day at noon. And syncing requires quite a bit of memory and CPU (75% of one vcpu)
So rather then starting the first sync manually at midnight, I would like something similar to jira's use of the quartz scheduler to specify a time, and not an interval.
Anyone found a way around this?
Have you looked into setting up a delegated connection from Crowd to LDAP.
This will eliminate those massive performance hits during a sync. It will instead be smaller incremental loads against your LDAP server.
Also what version of crowd are you using? There have been more recent releases that address this synching issue. Perhaps an upgrade would be able to address your performance concerns.
We looked at using the delegated directories but there was a limitation regarding how users are added. OUr business partners want to be able to @Mention or assign employees who may not have logged into a tool liek jIRA yet. Since we getn new employees contractors added on a regular basis this would be require a manual effort to perform manual imports on a regular basis.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs