Query metrics MBean

The query metrics MBean is useful for troubleshooting query performance, tuning the Solr configuration, such as the schema and caches, and tuning server resources, such as the JVM heap.

The query metrics MBean is useful for troubleshooting query performance, tuning the Solr configuration, such as the schema and caches, and tuning server resources, such as the JVM heap. The query metricsMBean records the amount of time spent to execute several main phases of distributed query on the index.

Main operational phases 

The main phases of a distributed query operation are:

  • COORDINATE

    Comprises the total amount of time spent by the coordinator node to distribute the query and gather/process results from shards. This value is computed only on query coordinator nodes.

  • EXECUTE

    Comprises the time spent by a single shard to execute the actual index query. This value is computed on the local node executing the shard query.

  • RETRIEVE

    Comprises the time spent by a single shard to retrieve the actual data from Cassandra. This value will be computed on the local node hosting the requested data.

Query metrics mbean operations 

The query metrics mbean measures latency in microseconds. Metrics can be grouped by query, by providing an additional query.name parameter. For example, assuming you are using a Solr core named demo.solr and have indexed a field named type, this URL provides the additional query.name parameter:

http://localhost:8983/solr/demo.solr/select/?q=type:1&query.name=myquery

All metrics collected under a given query name are recorded and retrieved separately, as shown in the following list of operations. If no query name is provided, all metrics are recorded together.

Operations are:

  • setEnabled(boolean enabled)

    Enables/disables metrics recording. Enabled by default.

  • isEnabled()

    Checks if metrics recording is enabled.

  • getLatencyPercentile(String phase, String query, double percentile)

    Gets a query latency percentile by its query name, which is optional and can be null, and phase.

  • getRecordedLatencyCount(String phase, String query)

    Gets the total count of recorded latency metrics by its query name, which is optional and can be null, and phase.

  • getUnrecordedLatencyCount()

    Gets the total count of unrecorded latency values due to exceeding the maximum tracked latency, which is 10 minutes.

  • resetLatency(String query)

    Resets latency metrics for the given query name, which is optional and can be null.

  • resetLatencies()

    Resets all latency metrics.

Query metrics mbean operations use the phase names previously listed.

Using mbeans to evaluate performance 

The following example shows how to use the mbeans on Linux to obtain information about performance while running the DataStax Solr stress test demo.

  1. Start a single Solr node.
  2. Start jconsole using the PID of the Solr node: For example:
    sudo jconsole 1284
  3. On Linux, for example, execute these scripts to run the Solr stress demo in dse-4.0.0/demos/solr_stress.
    ./1-add-schema.sh
./2-run-benchmark.sh --clients=10 --loops=10000 --type=both

    The demo creates a Solr core named demo.solr and indexes 50,000 documents.

  4. In jconsole, expand com.datastax.bdp > search > demo.solr.

    The CommitMetrics and QueryMetrics mbean items appear.

  5. In jconsole, in Search > demo.solr > CommitMetrics > Operations > getLatencyPercentile, type EXECUTE in the p0 text entry box and 0.95 in the p1 text entry box. Click the getLatencyPercentile button.

    The Operation return value, 582 microseconds, appears:



  6. Click OK.
  7. Query Solr 20,000 times using the query.name parameter. For example:
    curl "http://localhost:8983/solr/demo.solr/select/?q=type:1&query.name=myquery"
curl "http://localhost:8983/solr/demo.solr/select/?q=type:3&query.name=myquery"
  8. In jconsole, in Search > demo.solr > QueryMetrics Operations getLatencyPercentile, type EXECUTE in the p0 text entry box, myquery in the p1 text entry box, and 95.0 in the P2 text entry box.

    The Operation return value, 97 microseconds, appears.