m/
- Original Message
> From: Renee Sun
> To: solr-user@lucene.apache.org
> Sent: Fri, April 15, 2011 3:41:28 PM
> Subject: Re: partial optimize does not reduce the segment number to
>maxNumSegments
>
> sorry I should elaborate that earlier...
>
> in our producti
sorry I should elaborate that earlier...
in our production environment, we have multiple cores and the ingest
continuously all day long; we only do optimize periodically, and optimize
once a day in mid night.
So sometimes we could see 'too many open files' error. To prevent it from
happening, in
Why do you care? You haven't outlined why having the precise numbers
here is necessary. Perhaps with a higher-level statement of the problem
you're trying to solve we could make some better suggestions
Best
Erick
On Wed, Apr 13, 2011 at 5:23 PM, Renee Sun wrote:
> yeah, I can figure out the
yeah, I can figure out the segment number by going to stat page of solr...
but my question was how to figure out exact total number of files in 'index'
folder for each core.
Like I mentioned in previous message, I currently have 8 files per segment
(.prx .tii etc), but it seems this might change i
thanks!
It seems the file count in index directory is the segment# * 8 in my dev
environment...
I see there are .fnm .frq .fdt .fdx .nrm .prx .tii .tis (8) file extensions,
and each has as many as segment# files.
Is it always safe to calculate the file counts using segment number multiply
by 8?
As Hoss mentioned earlier in the thread, you can use the statistics page
from the admin console to view the current number of segments. But if you
want to know by looking at the files, each segment will have a unique
prefix, such as "_u". There will be one unique prefix for every segment in
the ind
ok I dug more into this and realize the file extensions can vary depending on
schema, right?
for instance we dont have *.tvx, *.tvd, *.tvf (not using term vector)... and
I suspect the file extensions
may change with future lucene releases?
now it seems we can't just count the file using any formul
: /tmp # ls /xxx/solr/data/32455077/index | wc ---> this is the
start point, 150 seg files
: 150 150 946
: /tmp # time curl
the number of files i nthe index directory is not the "number of
segments"
the number of segments is an internal lucene concept that impacts
Hi Hoss,
thanks for your response...
you are right I got a typo in my question, but I did use maxSegments, and
here is the exactly url I used:
curl
'http://localhost:8080/solr/97/update?optimize=true&maxSegments=10&waitFlush=true'
I used jconsole and du -sk to monitor each partial optimize, and
: I have a core with 120+ segment files and I tried partial optimize specify
: maxNumSegments=10, after the optimize the segment files reduced to 64 files;
a) the option you want to specify is "maxSegments" .. not "maxNumSegments"
http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes
10 matches
Mail list logo
