Oak Index Corrupted | Community
Skip to main content
venkatac93333
venkatac93333
Level 2
May 17, 2018
Solved

Oak Index Corrupted

  • May 17, 2018
  • 8 replies
  • 6556 views

Hi,

I am using AEM 6.4. I see oak index got corrupted due to an improper shutdown of the AEM. And i started a re-indexing of lucene but it is taking a long time with these repeated logs in the error log. How long will the indexing take and also how to verify if its re-indexing.

17.05.2018 19:04:28.729 *INFO* [async-index-update-fulltext-async] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Marking [/oak:index/lucene] as corrupt. The index is failing since Thu May 17 16:11:40 UTC 2018 ,0 indexing cycles, failed 2074 times, skipped 0 time

17.05.2018 19:04:28.732 *INFO* [async-index-update-fulltext-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Removing corrupt flag from index [/oak:index/lucene] which has been marked as corrupt since [2018-05-17T16:11:40.451Z]

17.05.2018 19:04:28.732 *INFO* [async-index-update-fulltext-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Reindexing will be performed for following indexes: [/oak:index/lucene]

17.05.2018 19:04:28.733 *INFO* [async-index-update-fulltext-async] org.apache.jackrabbit.oak.plugins.index.progress.NodeCounterMBeanEstimator Paths to be traversed includedPath : [/], excludedPaths : [/etc/workflow/instances, /jcr:system, /etc/replication, /var]

17.05.2018 19:04:28.733 *INFO* [async-index-update-fulltext-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Estimated node count to be traversed for reindexing under / is [144384]

Thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

There must be an exception logged as well (which is not part of your initial log excerpt), which indicates about the type of problem. Here it's just that there is an error and the indexer is trying again. Can you please check for a stacktrace / proper error message which gives more insight what's wrong with it?

(And yes, raising a Daycare ticket is appropriate if that's more than just a local developer system ...)

Jörg

8 replies

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
May 17, 2018

Time it would take for reindexing would be dependent on the content and type of content you have. Once the reindex is complete, You can go check the indexStats Jmx mbean  in the felix console or crxde for that index and reindex=false flag would be set

venkatac93333
venkatac93333Author
Level 2
May 17, 2018

I am seeing the async update is marking the index as corrupt and the re-index i initiated has been removing the flag which is happening repeatedly. that is why i am concerned if the re-indexing is working or not. How to check the progress of the it other than the logs.

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
May 17, 2018

You'll have to check the Async IndexStats bean which would give you better idea why this is repeating ? Go to system/console/jmx > Indexstats (async) and see at the bottom of the screen

venkatac93333
venkatac93333Author
Level 2
May 17, 2018

I see both the async index and full-text index is running and re-index is in init state. Should i pause the async index while re-indexing is in progress? and can i do it via the console itself?

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
May 18, 2018

No, this is the correct status for reindexing and indexstats show that it is initiation phase and would be in running state and next completed

wait for the reindexing to be completed and recheck these later

venkatac93333
venkatac93333Author
Level 2
May 18, 2018

It did nothing, i left it overnight and its worse now. I am not able to load the console page. Still seeing same errors in the error logs.

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
May 18, 2018

I would suggest to log a daycare ticket so that someone from support team can look at it dedicatedly. Messages here might not help but this would need a thorough analysis on the state of the system

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
May 18, 2018

There must be an exception logged as well (which is not part of your initial log excerpt), which indicates about the type of problem. Here it's just that there is an error and the indexer is trying again. Can you please check for a stacktrace / proper error message which gives more insight what's wrong with it?

(And yes, raising a Daycare ticket is appropriate if that's more than just a local developer system ...)

Jörg

    Terms & ConditionsAccessibility statement

    Loading footer...