Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Thu, 7 Mar 2013 17:03:54 -0800 (PST)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: solr-user@lucene.apache.org
Subject: Re: Any documentation on Solr MBeans?
In-Reply-To: 
 <CALd5WP94GiKJxwU6S_L2HZzOQzTwx7fOhpuDLwEXioE8z7oMUQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1303071700020.8753@frisbee>
References: 
 <CALd5WP94GiKJxwU6S_L2HZzOQzTwx7fOhpuDLwEXioE8z7oMUQ@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: I'm trying to monitor some Solr behaviour, using JMX.
: It looks like a great job was done there, but I can't find any
: documentation on the MBeans themselves.

In general, the stats exposed by the various MBeans are going to largely 
depend on the underlying plugin classes -- in most cases they are 
hopefully self explaining, but in cases where they aren't, your best bet 
is to skim the code.

: For example, DirectUpdateHandler2 attributes. What is the difference
: between "adds" and "cumulative_adds"? Is "adds" count the last X seconds
: only? or maybe "cumulative_adds" survives a core reload?

as mark mentioned, i don't think any stats survive a core reload, because 
almost everything implementing MBean is created/destroyed along with the 
core.  

In the specific case of DirectUpdateHandler2, the "cumulative_* 
stats refer to the total number for hte life of the DUH2 instance, which 
the non cumlative stats are reset on commit.

-Hoss