Infos:
- Used Zammad version: zammad -helm (13.0.2)
- Used Zammad installation type: helm
- Operating system: windows 11
- Browser + version: chrome + Version 144.0.7559.133
Expected behavior: we have migrated from other legacy system to zammad around 3.3 million tickets. we have rebuilded indexes like below
nohup bundle exec rake zammad:searchindex:rebuild[12] > /tmp/rebuild_12workers.log 2>&1 &
Indexing is comeplete but not able to view cases yet.
zammad@zammad-railsserver-7866bb8f47-29kgn:~$ curl -s ‘http://elasticsearch-master-hl:9200/_cat/indices?v’ | grep zammad_production_ticket
green open zammad_production_ticket QbZeNj4aR8CTRO71ve6pLg 1 1 3334618 0 8.8gb 4.4gb 4.4gb
green open zammad_production_ticket_state 0pq40qZ1SQCnN0dsTOieig 1 1 13 0 234.3kb 71.9kb 71.9kb
green open zammad_production_ticket_priority SsCwo8eMQWyMzkrfKw6P3Q 1 1 5 2 202.2kb 141.1kb 141.1kb
Actual behavior:
- with elastic search endpoints, it should fetch results of tickets.
Not sure this is important, but no aliases were found
zammad@zammad-railsserver-7866bb8f47-29kgn:~$ curl http://elasticsearch-master-hl:9200/_cat/aliases?v
alias index filter routing.index routing.search is_write_index
Steps to reproduce the behavior:
- NA
one more observation, i think it used to work with when we rebuild indexes without extra cores, since this was taking huge time we used multiple cores it did completed faster like ~12hrs but no response from elastic search endpoint.
Could anyone please help here? and also i would like to know full flow of zammad
wuth elastic search,redis,rubyrails etc any diagram to follow to understand exact flow.
thanks