Manticore Search 2.7.3 GA release

We are pleased to announce the release of Manticore Search 2.7.3 GA.

Prebuilt packages available for Debian,Ubuntu, Red Hat/CentOS, Windows and OSX can be downloaded from here.


  • CALL KEYWORDS result set can be sorted by docs/hits using sort_mode option.
  • DEBUG command can initiate a SIGEGV action (crash on demand) with ‘crash <password>’ subcommand when used on VIP connections. In addition, ‘malloc_stats’ subcommand can dump malloc information in searchd.log and malloc_trim can perform a malloc_trim() operation.
  • If GDB is present in the system, a more complete backtrace is logged. GDB is not a requirement for reporting issues. However in case a reported issue can’t be reproduced by the development team, backtraces that use gdb can provide more insights.


An important issue was related to increase of RSS memory over time in certain conditions when the default malloc was used. Several fixes (leaks and small refactors) address this issue and RSS should now be stable over time. Beside, a new round of memory leaks got fixed.

Several bug fixes were related to Percolate Queries feature. We’re glad to see our users are starting using this in production.

In total this release contains a record number of about 40 memory leaks, bugs and crashes fixed.

For a full report please consult the Release note.


Ongoing major features we are working on include:

  • Replication for PQ which will later be a base for other types indexes replication
  • PQ distributed indexes to make it easier to scale stream filtering horizontally
  • New index format which will provide much higher performance for some use cases. An index converter will also be available

If you’re interested for  private beta testing before the stable public beta, please let us know.

Leave a Reply


Personal and team training will maximize them performance. 

Custom development

Need cone custom or individual features?

Fill the form and don’t forget to make the description of what you need.

Free config review

There are often optimizations that can be made to a Sphinx / Manticore setup by changing some simple directives in the configuration or making quick changes to an index definition.

Some common mistakes and issues can include:

  • doing main+delta without kill-lists, even if the delta does include updated records found in the main
  • using wildcarding with very short prefix/infix which can hammer performance in some cases
  • disabled (unintentional) seamless rotates and getting stalls on index rotations
  • adding texts as string attributes even if they are not using for any kind of operation (filtering, grouping, sorting) or mandatory to be present in results
  • using deprecated settings 

Having a quick look on the configuration can show issues or potential issues, this is why we want to offer a gift to our growing community!

When uploading your configuration file, we recommend to remove any database credentials first.

We suggest also you give as many possible details about your setup: how big is the data you have, how typical queries look and what issues you experience.

Contact us