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 time around it restarts (Actually, it would have logged some error the first time around it hit the exception).
Otoh, if the index is covering property indices, then you might be hitting some other issue(s). Thanks, Vikas On Thu, Sep 15, 2016 at 12:29 AM, Thiago Sanches <[email protected]> wrote: > 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 #40000 ... > Reindexing Traversed #50000 ... > Reindexing Traversed #60000 ... > > This process are decreasing the system performance. > I could not find any information about that. > Could you have any advice? > > Thanks.
