I wish this helpful for you The contents of the cache is expunged when a new searcher is opened - usually when a commit or an optimize happens (where the underlying index has changed and you want those changes to be visible). The values in insert, hits, etc. are tracked for this specific searcher. In your example the size is currently 30 - and there has been 30 inserts - so nothing has been expunged from the cache because of overflow. The size given in the configuration is the maximum number of items the cache will hold, while the number in your JMX stat is the actual size of the cache. Since you have 0 in hits fields, etc., this cache has never had any decent use, since each request so far has lead to an insert instead of returning a lookup from the cache.
wish of those help The getSplitTime() method returns the latest split time. You should call it after the relevant split. However, I would measure every event with a new stopWatch (preferably in a single dedicated method), so that you don't have do subtract time durations to get the time per event.
it fixes the issue They are being indexed. There is a pre defined schema in the schema.xml file that it will be using. I have found search times to be very fast using Solr, with tens of thousands of docs.
I wish did fix the issue. Since I had the same question, here's what I found looking through the source code: milliseconds. In other places in Solr, totalTime is often used for values in milliseconds (see e.g. this comment in OfflineSorter.
it helps some times If you just want the info shown in the Admin interface, you can use the same endpoint as the admin interface - watch the network tab under your browser's developer tools as you navigate the interface. The interface is purely display oriented, all the data comes from API endpoints exposed in Solr. For core information this is by default:
wish helps you I was able to answer my own question by creating a simple app that tests the circuit breaker. The equation to determine when to open the circuit uses request volume threshold, error threshold percentage during the entire rolling stats timeInMilliseconds window. The buckets are only used for how/when the rolling window is updated.