You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 start an indexing over all your data or start an indexing over all not indexed data and you did not let open this browser tab open, refresh the browser tab to prevent issue #5179 and even did not navigate to an other site in the application the indexing goes into a never ending loop scenario as it could not start the next type of index when the current indexing type is finished. This can even happen if the indexing of a type is failing and the next indexing type would be started.
If you ran into such a case then you must restart the application, indexing the maybe remaining not indexed data sets as long you not encounter the issue #5177 and start the remaining index types in a manual way.
goal:
Indexing should not be depend on a open browser tab.
The text was updated successfully, but these errors were encountered:
If I understand correctly, this is a different wording for issue #3713. I had analyzed the problem there some time ago, see my last comment in that issue.
This could be possible but the old issue is from 2020 and maybe still related and / or similar to this one. As I opened this and the other indexing issues I wrote them down from an internal list and did not search for existing issues.
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 start an indexing over all your data or start an indexing over all not indexed data and you did not let open this browser tab open, refresh the browser tab to prevent issue #5179 and even did not navigate to an other site in the application the indexing goes into a never ending loop scenario as it could not start the next type of index when the current indexing type is finished. This can even happen if the indexing of a type is failing and the next indexing type would be started.
If you ran into such a case then you must restart the application, indexing the maybe remaining not indexed data sets as long you not encounter the issue #5177 and start the remaining index types in a manual way.
goal:
Indexing should not be depend on a open browser tab.
The text was updated successfully, but these errors were encountered: