Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.6

[X] +1 Approve the release alex On Tue, Jul 19, 2016 at 4:00 PM, Francesco Mari wrote: > Hi, > > We solved 5 issues in this release: > https://issues.apache.org/jira/browse/OAK/fixforversion/12337966 > > There are still some outstanding issues: >

Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.6

On 19.7.16 4:00 , Francesco Mari wrote: [X] +1 Approve the release Michael

Re: [VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.6

+1 2016-07-19 16:00 GMT+02:00 Francesco Mari : > Hi, > > We solved 5 issues in this release: > https://issues.apache.org/jira/browse/OAK/fixforversion/12337966 > > There are still some outstanding issues: > https://issues.apache.org/jira/browse/OAK/component/12329487 >

[VOTE] Release Apache Jackrabbit Oak Segment Tar version 0.0.6

Hi, We solved 5 issues in this release: https://issues.apache.org/jira/browse/OAK/fixforversion/12337966 There are still some outstanding issues: https://issues.apache.org/jira/browse/OAK/component/12329487 Staging repository:

Oak 1.5.6 release plan

Hello team, I'm planning to cut Oak 1.5.6 today in the afternoon british time. If there are any objections please let me know. Otherwise I will re-schedule any non-resolved issue for the next iteration. Sorry for late notice. Thanks Davide

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

[ANNOUNCE] Apache Jackrabbit Oak 1.4.5 released

The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit Oak 1.4.5 The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release: Release Notes -- Apache Jackrabbit Oak --

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.4.5

Hello Team, The vote passes as follows: +1 Marcel Reutegger +1 Vikas Saurabh +1 Dominique Jäggi Thanks for voting. I'll push the release out. -- Davide

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