Manticore Search 3.1.2 release

We are pleased to announce the release of Manticore Search 3.1.2. Downloads are available here and from the Manticore Github page. Docker image is available at Docker Hub.

New features

Experimental SSL support for HTTP API is now available.

A new listen interface https can be used. It offers the HTTP API over a secured HTTP connection. Server private key and certificate, optionally with CA certificate need to be set using the searchd ssl_cert, ssl_key and ssl_ca directives.

HTTP /json/search now accepts max_matches option.


Improved support for FreeBSD.

The default value for Galera gcache.size is sized to the biggest rt_mem_limit found among local indexes  or 16MB per  added index in the cluster. This should improve the speed of replication.

RPM packages can be installed for CentOS/RHEL 6/7 from our official yum repository.


A number of fixes are included in this release:

  • d0a7c959 fix #250 index_field_lengths index option for TSV and CSV piped sources
  • 4adc0752 fix flush rescheduling for indexes without activity
  • 553ca73c fix empty select list at SphinxQL query log
  • 0a1a2c81 fixed replication of RT index into node where same RT index exists and has different path
  • 1266d548 fix indextool wrong report for block index check on empty index

For  a full report please consult the Release note.

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