AEM upgrade from 6.1 to 6.3 - reindexing not working on publish instance | Community
Skip to main content
Level 2
August 1, 2017
Solved

AEM upgrade from 6.1 to 6.3 - reindexing not working on publish instance

  • August 1, 2017
  • 3 replies
  • 2425 views

Hello Everyone,

We are in the process of upgrading our system from AEM 6.1 to AEM 6.3. While running the in place upgrade process on the publish instance, the reindexing step goes into an infinite loop.

We are referring to the following document.

Upgrading to AEM 6.3

Following steps were performed on the publish instance:

1) We started the AEM 6.1 instance and ran the pre upgrade tasks.

2)  Performed tar compaction.

3)  Then we went ahead and ran the data migration step using file datastore option (quickstart jar of 6.3 was used). The migration was completed and successful.

4)  The next step was to start the instance using 6.3 quickstart jar. While staring the instance, one of the step involves reindexing. This is where it goes into an infinite loop and gets stuck.

Following is the information in upgrade.log:

29.07.2017 19:24:53.498 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.CQ62Html5SmartFileUpgrade Waiting indexing to be done for property xtype

Following is the information found in the error.log which gets repeated again and again:

31.07.2017 00:00:06.705 *WARN* [sling-oak-340-Registered Service.875] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate [async] Failed to retrieve previously indexed checkpoint c14abad2-56fc-4332-a197-ffb04b760460; re-running the initial index update

31.07.2017 00:00:06.706 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/socialLucene]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.707 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/workflowDataLucene]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.715 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Found a new index node [damFileSize]. Reindexing is requested

31.07.2017 00:00:06.715 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/slingeventJob]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.716 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Found a new index node [lsaPeople]. Reindexing is requested

31.07.2017 00:00:06.716 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/lsaPeople]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.716 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/versionStoreIndex]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.717 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/commerceLucene]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.718 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Found a new index node [counter]. Reindexing is requested

31.07.2017 00:00:06.718 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/authorizables]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.719 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Found a new index node [templateLucene]. Reindexing is requested

31.07.2017 00:00:06.719 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/templateLucene]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.719 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/cqProjectLucene]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.720 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Found a new index node [lsaNews]. Reindexing is requested

31.07.2017 00:00:06.720 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/lsaNews]. Changes in index definition would now only be effective post reindexing

31.07.2017 00:00:06.720 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Found a new index node [damLucene]. Reindexing is requested

31.07.2017 00:00:06.720 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexEditorContext Stored the cloned index definition for [/oak:index/damLucene]. Changes in index definition would now only be effective post reindexing

Could someone please help us figure out the issue here?

Thank you for your time.

Best Regards,

Ananta

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

Hi,

The log messages do not indicate any problem. Please note that the indexing can take a long time (based on many factors, repo size being probably the most prominent one).

Anyway, if you have problems with the upgrade process, please reach out to Daycare support; the process is tested quite well, so either your approach is not correct, or you hit an issue in the process, in which the support is most qualified to help.

For any other support we would need the relevant logfiles.

Jörg

3 replies

kautuk_sahni
Community Manager
Community Manager
August 2, 2017

Jörg Hoh​ any help here?

~kautuk

Kautuk Sahni
joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
August 2, 2017

Hi,

The log messages do not indicate any problem. Please note that the indexing can take a long time (based on many factors, repo size being probably the most prominent one).

Anyway, if you have problems with the upgrade process, please reach out to Daycare support; the process is tested quite well, so either your approach is not correct, or you hit an issue in the process, in which the support is most qualified to help.

For any other support we would need the relevant logfiles.

Jörg

smacdonald2008
Level 10
August 2, 2017

Great response Joerg!