Viewing the Solr core status
Using the Solr API to view the status of the Solr core.
http://localhost:8983/solr/#/~cores/wiki.solr
Status of all Solr cores
http://localhost:8983/solr/admin/cores?action=STATUS
{ "defaultCoreName":"default.1371321667755813000", "initFailures":{}, "status":{ "wiki.solr":{ "name":"wiki.solr", "isDefaultCore":false, "instanceDir":"solr/", "dataDir":"/var/lib/cassandra/data/solr.data/wiki.solr/", "config":"solrconfig.xml", "schema":"schema.xml", "startTime":"2013-06-16T21:05:54.894Z", "uptime":7212565, "index":{ "numDocs":3579, "maxDoc":3579, "deletedDocs":0, "version":532, "segmentCount":15, "current":false, "hasDeletions":false, "directory":"org.apache.lucene.store. NRTCachingDirectory:NRTCachingDirectory (org.apache.lucene.store.NIOFSDirectory @/private/var/lib/cassandra/data/solr.data/wiki.solr/index lockFactory= org.apache.lucene.store.NativeFSLockFactory@e3f6d; maxCacheMB=48.0 maxMergeSizeMB=4.0)", "userData":{"commitTimeMSec":"1371416801053"}, "lastModified":"2013-06-16T21:06:41.053Z", "sizeInBytes":8429726, "size":"8.04 MB"}, "indexing":false}}}
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. You can use densely packed DocValue field types and per-segment docsets. Facet queries will be per-segment, which improves real-time search performance problems.
&memory=true
to the URL used to view the status of Solr 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:http://localhost:8983/solr/admin/cores?action=STATUS&memory=true
Example 1
http://localhost:8983/solr/admin/cores?action=STATUS&wt=json&indent=on&omitHeader=on &memory=true . . . "memory":{ "unInvertedFields":{ "totalSize":0, "totalReadableSize":"0 bytes"}, "multiSegment":{ "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)", "fieldCache":{ "entriesCount":0}, "totalSize":0, "totalReadableSize":"0 bytes"}, "segments":{ "_6p":{ "segment":"_6p", "docValues":{ . . . "fieldCache":{ "entriesCount":0}, "totalSize":51600, "totalReadableSize":"50.4 KB"}}, "totalSize":619200, "totalReadableSize":"604.7 KB"}}, "totalMemSize":619200, "totalReadableMemSize":"604.7 KB"}}
Example 2
. . . "fieldCache":{ "entriesCount":1, "id":{ "cacheType":"org.apache.lucene.index.SortedDocValues", "size":260984, "readableSize":"254.9 KB"}}, "totalSize":260984, "totalReadableSize":"254.9 KB"}, "segments":{ . . . "fieldCache":{ "entriesCount":2, "age":{ "cacheType":"int", "size":3832, "readableSize":"3.7 KB"}, "id":{ "cacheType":"int", "size":3832, "readableSize":"3.7 KB"}}, "totalSize":59232, "totalReadableSize":"57.8 KB"}}, "totalSize":524648, "totalReadableSize":"512.4 KB"}}, "totalMemSize":524648, "totalReadableMemSize":"512.4 KB"}}
Using the field cache
In Lucene-Solr 4.5 and later, docValues are mostly disk-based to avoid the requirement for large heap allocations in Solr. If you use the field cache in sort, stats, and other queries, make those fields docValues.