Hello everyone,
I've changed OTRS Kernel::System::Ticket::IndexAccelerator from RuntimeDB to StaticDB and TicketStorage from DB to FS according to OTRS optimization recommendations (https://otrs.github.io/doc/manual/admin ... uning-otrs) recently.
Everything went fine, OTRS is working MUCH faster, DB size was 15G, now it is 1.1Gb. The only issue I have is the Search - when I'm making Full-text search, it returns results from the tickets that were delivered into OTRS after optimizations. This is only for full-text search, if I'm looking for ticket using its ticket number everything works fine.
What can be the reason of such behaviour of full-text search? Is it fixable?
Thanks in advance
[SOLVED] Full-text search returns incomplete results after optimizing OTRS
Moderator: crythias
[SOLVED] Full-text search returns incomplete results after optimizing OTRS
Last edited by jester on 08 Jul 2016, 10:08, edited 1 time in total.
OTRS 5.0.9 on CentOS 7.1 with MariaDB
-
reneeb
- Znuny guru
- Posts: 5018
- Joined: 13 Mar 2011, 09:54
- Znuny Version: 6.0.x
- Real Name: Renée Bäcker
- Company: Perl-Services.de
- Contact:
Re: Full-text search returns incomplete results after optimizing OTRS
Did you run ?
Code: Select all
perl bin/otrs.Console.pl Maint::Ticket::FulltextIndexRebuildPerl / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Re: Full-text search returns incomplete results after optimizing OTRS
Perfect, thank you reneeb!
It works now. I wonder why it is not in official documentation.
It works now. I wonder why it is not in official documentation.
OTRS 5.0.9 on CentOS 7.1 with MariaDB