Tuning DSE Search – Indexing latency and query latency (cassandra)

DSE offers out of the box search indexing for your Cassandra data. The days of double writes or ETL’s between separate DBMS and Search clusters are gone.

I have my cql table, I execute the following API call, and (boom) my cassandra data is available for:

1) full text/fuzzy search
2) ad hoc lucene secondary index powered filtering, and
3) geospatial search

Here is my API call:

$ bin/dsetool create_core <keyspace>.<table> generateResources=true reindex=true
or if you prefer curl (or are using basic auth) use the following:

$ curl "http://localhost:8983/solr/admin/cores?action=CREATE&name=<keyspace>.<table>&generateResources=true"
Rejoice! we are in inverted index, single cluster, operational simplicity bliss!

The remainder of this post will be focused on advanced tuning for DSE Search both for a) search indexing latency (the time it takes for data to be searchable after it has been inserted through cql), and b) search query latency (timings for your search requests).

Indexing latency
In this section I’ll talk about the kinds of things we can do in order to

1) instrument and monitor DSE Search indexing and

2) tune indexing for lower latencies and increased performance.

Source : www.datastax.com