[Bug 36898] New: Elasticsearch indexer error log needs more information
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36898 Bug ID: 36898 Summary: Elasticsearch indexer error log needs more information Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs@lists.koha-community.org Reporter: dcook@prosentient.com.au Fairly regularly I'm seeing the following message showing up in /var/log/koha/instance/es-indexer-output.log [2024/05/20 09:28:13] [WARN] Update of elastic index failed with: Exception 'Koha::Exceptions::Elasticsearch::BadResponse' thrown 'Bad response received when submitting request to Elasticsearch' with details => [https://hostname:9300]-[599] Timed out while waiting for socket to become ready for reading, type => Timeout main::catch {...} /usr/share/koha/bin/workers/es_indexer_daemon.pl (229) But this doesn't really tell me anything useful. It's not clear what records failed to update or what the job number was, so there's no way to re-try and fix the missing indexed data. Also, I've updated the request_timeout from 30 to 60, so it's a fairly long timeout. Generally speaking, there was a fair amount of indexing activity, but around 09:27:13 there wasn't. Although there was 6 jobs at 09:28:13, so maybe it's not the request_timeout that needs tweaking... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36898 --- Comment #1 from David Cook <dcook@prosentient.com.au> --- "Timed out while waiting for socket to become ready for reading" comes from HTTP::Tiny, which is the HTTP client used by Search::Elasticsearch. The only direct mention I've found for it is on the Elastic discussion forms for "Elasticsearch - Error Timeout 599". (Not including the link so that Bugzilla doesn't block me.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36898 --- Comment #2 from David Cook <dcook@prosentient.com.au> --- Actually, I forgot I'd also found a mention on the elasticsearch-perl Github for issue "reindex timeout #112" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36898 Emmi Takkinen <emmi.takkinen@koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emmi.takkinen@koha-suomi.fi -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36898 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michaela.sieber@kit.edu -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36898 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- It sounds like the bug description is a bit misleading/sounds too harmless, isn't the real problem here that we are missing records to index? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36898 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from David Cook <dcook@prosentient.com.au> --- Yeah, I think I was barking up the wrong tree here... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org