Hi Radim,
To address your comment about JIRA and search - perhaps this is better
- and it finds you:
http://search-lucene.com/?q=throttle+mergefc_project=Solr
Otis
--
Search Analytics - http://sematext.com/search-analytics/index.html
Performance Monitoring - http://sematext.com/spm/index.html
Dne 29.10.2012 0:09, Lance Norskog napsal(a):
1) Do you use compound files (CFS)? This adds a lot of overhead to merging.
i do not know. whats solr configuration statement for turning them on/off?
2) Does ES use the same merge policy code as Solr?
ES rate limiting:
is there JIRA ticket dedicated to throttling segment merge? i could not
find any, but jira search kinda sucks.
It should be ported from ES because its not much code.
Is there way to set-up logging to output something when segment merging
runs?
I think segment merging is logged when you enable infoStream logging
(you
should see it commented in the solrconfig.xml)
no, segment merging is not logged at info level. it needs customized log
config.
INFO
With Lucene 4.0, FSDirectory now supports merge bytes/sec throttling
(FSDirectory.setMaxMergeWriteMBPerSec): it rate limits that max
bytes/sec load on the IO system due to merging.
Not sure if it's been exposed in Solr / ElasticSearch yet ...
Mike McCandless
http://blog.mikemccandless.com
On
Dne 29.10.2012 12:18, Michael McCandless napsal(a):
With Lucene 4.0, FSDirectory now supports merge bytes/sec throttling
(FSDirectory.setMaxMergeWriteMBPerSec): it rate limits that max
bytes/sec load on the IO system due to merging.
Not sure if it's been exposed in Solr / ElasticSearch yet ...
, October 27, 2012 7:44:46 PM
| Subject: Re: throttle segment merging
|
| Dne 26.10.2012 3:47, Tomás Fernández Löbbe napsal(a):
| Is there way to set-up logging to output something when segment
| merging
| runs?
|
| I think segment merging is logged when you enable infoStream
| logging (you
| should
Dne 26.10.2012 3:47, Tomás Fernández Löbbe napsal(a):
Is there way to set-up logging to output something when segment merging
runs?
I think segment merging is logged when you enable infoStream logging (you
should see it commented in the solrconfig.xml)
no, segment merging is not logged at info
Is there way to set-up logging to output something when segment merging
runs?
I think segment merging is logged when you enable infoStream logging (you
should see it commented in the solrconfig.xml)
Can be segment merges throttled?
You can change when and how segments are merged with the
