Further issues on FTS engine
Hi,
Additionally to the long list of problem on the FTS previously discussed, here a new:
WHen I reset the indexes, the indexer-worker seems paralelleizing the indexing (which is good), however, the number available in "ps aux | grep dove" shows that it does not move:
dovecot 28549 0.0 0.0 8620 3920 ? S 06:20 0:00 dovecot/indexer [0 clients, 3 requests] mailuse+ 28550 98.6 0.1 167412 86916 ? R 06:20 5:28 dovecot/indexer-worker [jom@grosjo.net XXXX - 800/37755]
Looking further, if I put a tracer in teh backend, it treats the *same* message several times in parallel, and therefore does not move very fast on the global indexing of the box
ANy clue ?
THanks
On 20/05/2019 08:27, Joan Moreau via dovecot wrote:
Hi,
Additionally to the long list of problem on the FTS previously discussed, here a new:
WHen I reset the indexes, the indexer-worker seems paralelleizing the indexing (which is good), however, the number available in "ps aux | grep dove" shows that it does not move:
dovecot 28549 0.0 0.0 8620 3920 ? S 06:20 0:00 dovecot/indexer [0 clients, 3 requests] mailuse+ 28550 98.6 0.1 167412 86916 ? R 06:20 5:28 dovecot/indexer-worker [jom@grosjo.net XXXX - 800/37755]
Looking further, if I put a tracer in teh backend, it treats the *same* message several times in parallel, and therefore does not move very fast on the global indexing of the box
ANy clue ?
THanks
Hi Joan
which version of dovecot are you using? I tried running ps aux | grep dove on latest version but I don't see this behaviour.
Can you post some evidence of the same message being indexed serveral times in parallel?
John
participants (2)
-
Joan Moreau
-
John Fawcett