Adobe Experience Manager: Many index update messages appear after upgrading to AEM 6.5 LTS SP1

Description description

After upgrading to AEM 6.5 LTS SP1, an index log message that did not appear previously may start to appear. This article explains why AEM logs this message and how to handle it.

Example:
*INFO* [ async-index-update-fulltext-async] org.apache.jackrabbit.oak.plugins.index.lucene.writer.DefaultIndexWriter Creating writer for index: /oak:index/lucene. Config: matchVersion=LUCENE_47_analyzer=org.apache.lucene.analysis.miscellaneous.PerFieldAnalyzerWrapper_ramBufferSizeMB=16.0_maxBufferedDocs=-1_maxBufferedDeleteTerms=-1_mergedSegmentWarmer=null_readerTermsIndexDivisor=1_termIndexInterval=32_delPolicy=org.apache.lucene.index.KeepOnlyLastCommitDeletionPolicy_commit=null_openMode=CREATE_OR_APPEND_similarity=org.apache.lucene.search.similarities.DefaultSimilarity_mergeScheduler=ConcurrentMergeScheduler: maxThreadCount=1, maxMergeCount=1, mergeThreadPriority=-1_default WRITE_LOCK_TIMEOUT=1000_writeLockTimeout=1000_codec=Lucene46_infoStream=org.apache.lucene.util.InfoStream$NoOutput_mergePolicy=[ TieredMergePolicy: maxMergeAtOnce=10, maxMergeAtOnceExplicit=30, maxMergedSegmentMB=5120.0, floorSegmentMB=2.0, forceMergeDeletesPctAllowed=10.0, segmentsPerTier=10.0, maxCFSSegmentSizeMB=8.796093022207999E12, noCFSRatio=0.1_indexerThreadPool=org.apache.lucene.index.ThreadAffinityDocumentsWriterThreadPool@5dfc633e_readerPooling=false_perThreadHardLimitMB=1945_useCompoundFile=true_writer=org.apache.lucene.util.SetOnce@5781a466_

Environment
AEM 6.5 LTS SP1

Resolution resolution

When AEM starts an index update, it creates a DefaultIndexWriter and logs this message.

In AEM 6.5 LTS SP1, this message is logged at the INFO level instead of TRACE. As a result, the message appears more frequently in the logs and, in some cases, a large number of log lines can appear. This message simply reports index update activity and does not indicate any error or defect.

If the log file size is a concern, reduce the number of occurrences of this message by changing the log level for org.apache.jackrabbit.oak.plugins.index.lucene.writer.DefaultIndexWriter to WARN in the logging configuration.

Note that this change removes the corresponding log information while the WARN level remains in effect. If these details are required later for troubleshooting, adjust the log configuration again to enable more detailed log messages.