mostly status of the indexes, whether there is some corruption or all is ok.
On Thu, Apr 14, 2011 at 9:20 PM, Simon Willnauer < simon.willna...@googlemail.com> wrote: > what kind of diagnostics are you looking for? > > simon > > On Thu, Apr 14, 2011 at 9:14 PM, jm <jmugur...@gmail.com> wrote: > > Thanks Erick, but I guess what you refer to lives in Solr right? I am > using > > plain Lucene. > > > > On Thu, Apr 14, 2011 at 7:33 PM, Erick Erickson <erickerick...@gmail.com > >wrote: > > > >> What information do you need? Could you just ping the stats component > >> and parse the results (basically the info on the admin/stats page). > >> > >> Best > >> Erick > >> > >> On Thu, Apr 14, 2011 at 11:56 AM, jm <jmugur...@gmail.com> wrote: > >> > >> > Hi, > >> > > >> > I need to collect some diagnostic info from customer sites, so I would > >> like > >> > to get info on the status of lucene indexes...but I don't want the > >> process > >> > of collecting to take very long. > >> > > >> > So I am considering Checkindex. I tested in a small index (60k docs) > and > >> it > >> > took 12 seconds. A site usually has up to 100 indexes (indexes have 6 > >> > fields) so running it for every index like this is unfeasible. > >> > > >> > Is there a way to make is faster (even if it verifies less things?). > Is > >> the > >> > time Checkindex will take proportional to number of docs? I am on > Lucene > >> > 3.1 > >> > > >> > thanks > >> > > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >