and more in a single search tool across platforms. Read the announcement here. |
01/15/2024 05:30 PM
Hello,
We may need to provision about 50,000 tasks to Azure AD simultaneously.
These tasks are primarily Add Access, including Create Account, Disable account, and Remove Access.
To validate, we actually generated about 34,000 tasks and ran provisioning jobs.
But in one job, all the tasks were not digested, and we had to pass the jobs around many times.
1st: 16:05~16:55 Completed about 8,000 tasks
2nd: 18:31~20:27 Completed about 10,000 tasks
3rd: 21:10~22:56 Completed about 8,000 tasks
4th: 23:00~01:09 Completed about 8,000 tasks
・
・
・
Looking at this result, it seems that only about 8,000 tasks are targeted in 1 job in about 2 hours.
Is there a way to complete this in 1 job?
01/15/2024 05:41 PM
It will remain in queue after some hours it will be clear out. even having one job on UI in processing it will take time to process all task so it will be in queue
01/15/2024 05:50 PM
Hi rushikeshvartak,
If running job is 0, does that mean it's actually a single provisioning job that continues to run?
(Does that mean I don't have to run the provisioning job multiple times?)
01/15/2024 05:52 PM - edited 01/15/2024 05:52 PM
Yes same job will keep all tasks in queue
You can enable multi threading for wsretry from external config properties file
# Configs to enable WSRetry multi-threading
enablemultithreadinginwsretry=true
#provisioningjobcount=10
01/15/2024 07:00 PM
Isn't the standard provisioning job (WSRETRYJOB) originally multi-threaded?
I know there are separate single-threaded provisioning jobs, but I don't currently use them.
Or does this setting upgrade my current provisioning job?
01/15/2024 07:01 PM
By default multi threaded provisioning is disabled