| Summary: | Elasticsearch not reindexing biblios when add or modify record | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Daniel <ulmerdan> |
| Component: | Searching - Elasticsearch | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | dcook, magnus |
| Version: | 22.11 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Daniel
2024-06-10 19:23:18 UTC
Do you have the ES indexer worker running? I think deletes are sent directly to ES from the web app, so that would be why the deletes are working. I'm not sure about the authorities... We (the company I work at) have had issues with Elasticsearch on one server as well, although our issue appears to relate to timeouts. I'm still investigating that one... Dp you see background jobs related to Elasticsearch on /cgi-bin/koha/admin/background_jobs.pl, and are they marked as done/finished? Thanks for your responses. I see now the background_jobs "Update Elasticsearch index" are all staged and not executing. Status = "new", progress = "null/1", and started/ended fields are blank. Is there a setting or another method to have these run in real time? Note, I'm not familiar with the ES indexer worker. Is this applicable if my ES nodes are on a different server? (In reply to Daniel from comment #3) > Thanks for your responses. I see now the background_jobs "Update > Elasticsearch index" are all staged and not executing. Status = "new", > progress = "null/1", and started/ended fields are blank. Is there a setting > or another method to have these run in real time? > > Note, I'm not familiar with the ES indexer worker. Is this applicable if my > ES nodes are on a different server? There's just the background queue. Currently, no way to do it in real time from the web app (although sometimes I think we should add such a setting for single record modifications). How have you installed Koha? If you're using the Debian packages, you can run a command like "koha-es-indexer --start --quiet $(koha-list --enabled --elasticsearch)" This command is automatically run when the "koha-common" service is started. In your /var/log/koha/<instance>/ directory there should be files like es-indexer-error.log and es-indexer-output.log Overall, I think that this is probably a support query rather than a bug report. I'd suggest you explore the support options: https://koha-community.org/support/ |