DataStax Enterprise 3.1 Documentation

Viewing the status of the Solr core

This documentation corresponds to an earlier product version. Make sure this document corresponds to your version.

Latest DSE documentation | Earlier DSE documentation

You can use the Solr API to view the status of the core. For example, to view the status of the wiki.solr core after running the wikipedia demo, use this URL:



Viewing the status of all cores

To view the status of all cores use this URL:


For example, the status of the wiki.solr core looks like this:


           @/private/var/lib/cassandra/data/ lockFactory=
             maxCacheMB=48.0 maxMergeSizeMB=4.0)",
           "size":"8.04 MB"},

Viewing the status of field cache memory

The Solr field cache caches values for all indexed documents, which if left unchecked, can result in out-of-memory errors. For example, when performing faceted queries using multi-valued fields the multiValued fields are multi-segmented (as opposed to single segmented single-valued fields), resulting in an inefficient near real time (NRT) performance. In DataStax Enterprise 3.1 and later, you can use densely packed DocValue field types (introduced in Solr 4.2) and per-segment docsets. Facet queries will be per-segment, which improves real-time search performance problems.

To ensure that the jvm heap can accommodate the cache, monitor the status of the field cache and take advantage of the Solr 4.3 option for storing the cache on disk or on the heap. To view the status of the field cache memory usage, append &memory=true to the URL used to view the status of cores. For example, to view the field cache memory usage of the DSE Search quick start example after running a few facet queries, use this URL:


Example 1

For example, the URL for viewing the field cache memory usage in json format and the output is:


. . .

      "totalReadableSize":"0 bytes"},
      "multiSegment":"StandardDirectoryReader(segments_3:532:nrt _6p(4.3):
      C3193 _71(4.3):C161 _6i(4.3):C15 _6n(4.3):C21 _6e(4.3):C16 _6k(4.3):
      C19 _6t(4.3):C17 _6g(4.3):C10 _77(4.3):C12 _6v(4.3):C9 _7c(4.3):
      C66 _72(4.3):C14 _6x(4.3):C7 _6y(4.3):C7 _6w(4.3):C12)",
      "totalReadableSize":"0 bytes"},
        . . .

        "totalReadableSize":"50.4 KB"}},
    "totalReadableSize":"604.7 KB"}},
"totalReadableMemSize":"604.7 KB"}}

Example 2

After running a few sort by query functions, the output looks something like this:

. . .

          "readableSize":"254.9 KB"}},
      "totalReadableSize":"254.9 KB"},

. . .

            "readableSize":"3.7 KB"},
            "readableSize":"3.7 KB"}},
        "totalReadableSize":"57.8 KB"}},
    "totalReadableSize":"512.4 KB"}},
"totalReadableMemSize":"512.4 KB"}}