My Oracle Support Banner

Need Statistics About Esindex And Esrepair Tasks (Doc ID 2735557.1)

Last updated on DECEMBER 11, 2020

Applies to:

Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.

Symptoms


Currently, there are no statistics available about esindex and esrepair tasks.

An in-place upgrade is being performed from ISS to Elasticsearch on a UAT backend.
No "imcheck -g" commands have been run to force indexing.
An 'imcheck -q | grep -c " es"`was run to see if/when it would finish indexing folders automatically based on activity.
Also ran `imcheck -q | grep " es" |awk '{print $2}' | sort | uniq -c | sort -n` to watch and see how many have duplicate tasks.

An in-place upgrade in production is not planned, however, at some future point, the need to rebuild Elasticsearch may be a possibility. That would be basically the same as an in-place upgrade.
If some statistics about how long it is taking to index (or repair) individual folders could be gathered, it could provide an idea of how much longer it would potentially take and maybe gauge how long it would take to do a rebuild.
 
Messages like the following were observed:


But there is nothing observed about when esrepair is started or about when either of them end.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.