Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

query on Elasticsearch and Zammad #190

Closed
abhi15behera opened this issue Jun 23, 2023 · 1 comment
Closed

query on Elasticsearch and Zammad #190

abhi15behera opened this issue Jun 23, 2023 · 1 comment

Comments

@abhi15behera
Copy link

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

@monotek
Copy link
Member

monotek commented Jun 23, 2023

data should be pushed into elasticsearch by railsserver or scheduler.

but please use the forum for such quetsions: https://community.zammad.org/

@monotek monotek closed this as completed Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants