Re: Specifying threadpool name for periodic scheduled jobs (OAK-4563)

On Tue, Jul 19, 2016 at 1:44 PM, Stefan Egli wrote: > I'd go for #A to limit cross-effects between oak and other layers. Note that for #4 there can be multiple task scheduled. So if a system has 100 JCR Listeners than there would be 1 task/listener to manage the time

Re: Specifying threadpool name for periodic scheduled jobs (OAK-4563)

I'd go for #A to limit cross-effects between oak and other layers. The reason one would want to use the default pool for #4 is probably the idea that you'd want to avoid "wasting" a thread in the oak-thread-pool and rather rely on a shared one. But arguably, that should be an optimization of the

Re: Specifying threadpool name for periodic scheduled jobs (OAK-4563)

Hi, > Now should we use > > A - one single pool for all of the above > B - use the pool only for 1-3. The default pool would be of 5. So even > if #2 #3 are running > it would not hamper #1 While I'd want option#B to a better option, but I'd like to add one quick bit - we'd need to also

Re: Specifying threadpool name for periodic scheduled jobs (OAK-4563)

On Tue, Jul 19, 2016 at 1:21 PM, Michael Dürig wrote: > Not sure as I'm confused by your description of that option. I don't > understand which of 1, 2, 3 and 4 would run in the "default pool" and which > should run in its own dedicated pool. #1, #2 and #3 would run in

Re: Specifying threadpool name for periodic scheduled jobs (OAK-4563)

On 19.7.16 9:26 , Chetan Mehrotra wrote: On Tue, Jul 19, 2016 at 12:54 PM, Michael Dürig wrote: For blocking or time intensive tasks I would go for a dedicated thread pool. So wrt current issue that means option #B ? Not sure as I'm confused by your description of

Re: Specifying threadpool name for periodic scheduled jobs (OAK-4563)

On Tue, Jul 19, 2016 at 12:54 PM, Michael Dürig wrote: > For blocking or time intensive tasks I would go for a dedicated thread pool. So wrt current issue that means option #B ? Chetan Mehrotra

Re: Specifying threadpool name for periodic scheduled jobs (OAK-4563)

On 19.7.16 6:55 , Chetan Mehrotra wrote: Now currently in Oak we use following types of periodic jobs 1. Async indexing - (Cluster Singleton) 2. Document Store - Journal GC (Cluster Singleton) 3. Document Store - LastRevRecovery 4. Statistic Collection - For timeseries data update in

Specifying threadpool name for periodic scheduled jobs (OAK-4563)

Hi Team, While running Oak in Sling we rely on Sling Scheduler [1] to execute the periodic jobs. By default Sling Scheduler uses a pool of 5 threads to run all such periodic jobs in the system. Recently we saw an issue OAK-4563 where due to some reason the pool got exhausted for long time and