Re: large search indexer tasks, submitted to flatcurve+tika+tesseract backend for attachment scanning, timeout even with "fts_index_timeout = 0"; how to increase/remove timeouts?

On 07/23/2022 8:25 AM MDT PGNet Dev pgnet.dev@gmail.com wrote:

i'm running dovecot 2.3.19.1

[snip]

when i exec large reindex jobs, i get occassional timeout errors on dovecot's indexer-worker connection to tiks backend, e.g.,

2022-07-23 09:54:43 indexer-worker(postmaster@example.com): Error: fts_tika: PUT http://127.0.0.1:9998/tika/ failed: Request timed out (Request queued 61.031 secs ago, 1 send attempts in 60.103 secs, 60.080 in http ioloop, 0.000 in other ioloops, connected 60.103 secs ago) 2022-07-23 09:54:43 indexer-worker(postmaster@example.com): Error: Mailbox Sent: Precache for UID=90782 failed: Internal error occurred. Refer to server log for more information. [2022-07-23 09:54:43] (attempted to index 2 messages between UIDs 90778..90782)

i don't see any fts timeout info @

https://wiki.dovecot.org/Timeouts

here

https://doc.dovecot.org/settings/plugin/fts-plugin/#plugin_setting-fts-fts_i...

  "
  fts_index_timeout

          Default: 0

          Values: Unsigned integer

      When the full text search backend detects that the index isn’t up-to-date, the indexer is told to index the messages and is given this much time to do so. If this time limit is reached, an error is returned, indicating that the search timed out during waiting for the indexing to complete: NO [INUSE] Timeout while waiting for indexing to finish

      A value of 0 means no timeout.
  "

[snip]

where do I set that timeout to not fail, as above, on large index tasks?

You need to change the source, as Tika has a hardcoded 60 second HTTP request limit.

https://github.com/dovecot/core/blob/release-2.3.19/src/plugins/fts/fts-pars...

michael