Increasing the Indexing Speed / Count about zammad-helm HOT 4 CLOSED

Indexing happens in order and thus there is no such thing as increasing from 100 to 200 as example.
The searchindex process just reports in 100 steps to give you feedback about the state.

There's an environment that stops docker from constantly re-indexing on restarts (which is useless on big environments -especially- if you have proper control over your environment). Keep in mind that you have to reindex on your own.

from zammad-helm.

@MrGeneration Thank you for the information. With that said Tweaking all the parameter on Elasticsearch or Postgres doesnt just increases the steps. Because we have almost 1.1 Million tickets and re-indexing those take almost a minimum of 6-7 Hours. As per helm i have set the re-indexing to false so that upon restart of the zammad app pod doesnt re build the indexing as it will again take 6-7 Hours. Is there a method to reduce the Doc counts in Elasticsearch as i understand the "Zammad_production_ticket" is where all the ticket get indexed. Even if the tickets are closed we still might need to have that in the elastic in order to be fetched during the search in Zammad.

from zammad-helm.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from zammad-helm.

Hi @abhi15behera, if I understand your request correctly, it is not about zammad-helm, but instead about the Zammad product itself. Please head over to https://community.zammad.org/ to ask questions or place feature requests, or get in touch with us via zammad.com if you require commercial support.

from zammad-helm.