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
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Version of Helm and Kubernetes: 3.0+ and 1.21
What happened: Upon bulk update on the ticket the elasticsearch stops indexing any new ticket creation
What you expected to happen: The Indexing should be constant
How to reproduce it (as minimally and precisely as possible): Bulk deletion of ticket along with creation of ticket
Anything else we need to know: I would like to know how the Elasticsearch picks up the data from Zammad, is it through the Zammad Cache (redis & Memchached) or the Postgres because as the post bulk update happens the DB get updated and then the indexing stops and after the bulk update completes after certain interval the indexing starts for the new ticket as well as the updated tickets
The text was updated successfully, but these errors were encountered:
Is this a request for help?: Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Version of Helm and Kubernetes: 3.0+ and 1.21
What happened: Upon bulk update on the ticket the elasticsearch stops indexing any new ticket creation
What you expected to happen: The Indexing should be constant
How to reproduce it (as minimally and precisely as possible): Bulk deletion of ticket along with creation of ticket
Anything else we need to know: I would like to know how the Elasticsearch picks up the data from Zammad, is it through the Zammad Cache (redis & Memchached) or the Postgres because as the post bulk update happens the DB get updated and then the indexing stops and after the bulk update completes after certain interval the indexing starts for the new ticket as well as the updated tickets
The text was updated successfully, but these errors were encountered: