indexing - not successful index remaining not indexed objects

[henning-gerhardt]

preface:
The following issue may only occur if you indexing a few ten thousand to million entries and / or adjust the elastic search configuration entries in kitodo_config.properties not correct or not fitting to your amount of data.

description:
If you want to index the not indexed objects to complete the whole indexing of a type and the amount of to be indexed objects is above the value of elasticsearch.batch and elasticsearch.indexLimit then this kind of indexing is causing errors like out-of-index or never ending indexing loops. If you ran into this situation then you must restart the application so many times until the amount of not indexed objects is below the configurated batch or indexLimit values. One reason but not the only one is the static initialisation of the worker list in the IndexingService class and the use of the method countDatabaseObjects() of this class to determinate the amount of the indexed and not indexed objects.

goal:
Indexing not indexed objects should be implemented in a correct way that this is handling all use case scenarios correct from indexing the remaining amount of only one indexing type up to indexing all not indexed data and everything else.