Re: Infinite loop

On Thu, Sep 15, 2016 at 2:17 AM, Thiago Sanches wrote: > This issue start to appers after some problemas with disk space and some > force restarts on AEM. Do you see presence of ".bak" files in segmentstore folder post system restart after unclean shutdown with creation time

Re: IndexEditorProvider behaviour question.

Note that so far LuceneIndexEditor was used only for async indexing case and hence invoked only on leader node every 5 sec. So performance aspects here were not that critical. However with recent work on Hybrid indexes they would be used in critical path and hence such aspects are important On

Re: CommitHooks as OSGi Components.

On Thu, Sep 15, 2016 at 1:15 AM, Rob Ryan wrote: > Last I heard even local events can be subject to loss of the user id if so > many events are being processed that ‘compaction’ is used to mitigate the > load. Is this still the case? > > Please don’t point people toward the

Re: Infinite loop

Hi Thiago, > This issue start to appers after some problemas with disk space and some > force restarts on AEM. Just to confirm: does the drive which contains folder have sufficient space now? Any chance that AEM process can't write to /repository/index/* folders? > The Oak Core version is:

Re: Infinite loop

Hi Thiago, > By property indices did you mean the 'propertyIndex' attribute? No, I had meant value of "type" and "async" property on the index definition - in your case it's "lucene" and "async" respectively. > Caused by: java.io.FileNotFoundException: segments_3lxu > at >

Re: Infinite loop

Just to let you know. We enabled the debug for async index and here are the result: 14.09.2016 19:57:05.073 *DEBUG* [pool-12-thread-5] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Running background index task async 14.09.2016 19:57:05.074 *DEBUG* [pool-12-thread-5]

Re: Infinite loop

Hello Vikas, thanks for your reply. By property indices did you mean the 'propertyIndex' attribute? For example, we are using the following index definition: http://jackrabbit.apache.org/oak/ns/1.0; xmlns:sling="http://sling.apache.org/jcr/sling/1.0; xmlns:jcr="http://www.jcp.org/jcr/1.0;

Re: CommitHooks as OSGi Components.

Last I heard even local events can be subject to loss of the user id if so many events are being processed that ‘compaction’ is used to mitigate the load. Is this still the case? Please don’t point people toward the availability of the user id from events (without full disclaimers) if it will

Re: Infinite loop

Hi Thiago, That most often happens with async index updates. Logger name in this case for log message for the loop you're describing would have "AsyncIndexUpdate". You can enabled DEBUG log for "org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate" which should then log an exception the next

Infinite loop

Hello guys, I'm new with oak indexes and I'm using it with Adobe AEM. Here we created some indexes that it's seems that they are stucked in a infinite looping for example: Reindexing Traversed #4 ... Reindexing Traversed #5 ... Reindexing Traversed #6 ... This process are decreasing

Re: Minimum JDK version for 1.4

On 14/09/2016 12:27, Julian Reschke wrote: > should we consider allowing JDK7 features in 1.4 as well? I'm perfectly fine with it. It looks like no one noticed the error and it's relatively low risk for 1.4. JD7 has been around for a while now. I would simply add a note on the download page

Re: Minimum JDK version for 1.4

Hi, On 14/09/16 13:27, Julian Reschke wrote: So we now enforce JDK7 compliance on trunk, and JDK6 compliance on the release branches (1.0, 1.2, 1.4). Given the fact that we already shipped two releases of 1.4 which did require JDK7 features (and apparently nobody noticed), should we consider

Minimum JDK version for 1.4

On 2016-09-12 14:09, Marcel Reutegger wrote: Hi, On 12/09/16 13:14, Chetan Mehrotra wrote: I think Marcel created OAK-4791 for the same. So that should take care of enforcing this constraing Indeed. For trunk I just enabled the check against the 1.7 signature. I will backport the plugin

IndexEditorProvider behaviour question.

Hi, The behaviour of calls to the IndexEditorProvider appears to be suboptimal. Has this area been looked at before? I am working from a complete lack of historical knowledge about the area, so probably don't know the full picture. Based on logging the calls into

Re: [VOTE] Release Apache Jackrabbit Oak 1.5.10

On 2016-09-13 16:02, Davide Giannella wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.5.10 Best regards, Julian