esponse(even with
waitFlush=true) - i am doubting if optimization really happened , but
details on statistics page shows me correct number of segments.
On Tue, Mar 12, 2013 at 8:34 PM, Shawn Heisey-4 [via Lucene] <
ml-node+s472066n4046834...@n3.nabble.com> wrote:
> On 3/12/2013 4:17 PM, f
Hi Shawn,
I tried optimizing using this command...
curl
'http://localhost:/solr/update?optimize=true&maxSegments=10&waitFlush=true'
And i got this response within secs...
0840
Is this a valid response that one should get ?
I checked the statistics link from /solr/admin page and it show
Also, Is it absolutely necessary to set the maxSegments=1 , if we need to
reformat the whole index ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-Solr3-5-to-Solr4-1-Index-Reformat-tp4046391p4052991.html
Sent from the Solr - User mailing list archive at Nabble.com
Hello,
We are planning to upgrade our solr servers from version 3.5 to 4.1.
We have master slave configuration and the index size is quite big (i.e.
around 14 GB ).
1. Do we really need to re-format the whole index , when we upgrade to 4.1 ?
2. What will be the consequences - if we do not re-forma
Thanks Shawn.
So if we have new segments in 4.1 format and all old files in 3.5 format at
the same time, then will it cause any performance degradation on slaves
while reading index files ( which will contain both 3.5 formatted and 4.1
formatted files)?
--
View this message in context:
http://
Thanks Tomas!
I see the latest available version is 4.1 - but you have suggested a 4.2
version, where can i grab 4.2 version from?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-Solr3-5-to-Solr4-1-Index-Reformat-tp4046391p4046471.html
Sent from the Solr - User maili
Thanks Tomas/Shawn!
One more question related to backward compatibilty.
Previously we had upgraded our solr master/slaves from 1.4 version to 3.5
version - We didn't reformat the whole index then. So i believe there will
be some files with 1.4 format present in our index.
Now when we upgrade from
Hi Shawn,
Do we really need to optimize in order to reformat ?
If yes, What is the best way of optimizing index - Online or Offline ?
Can we do it online ? If yes -
1. What is the http request which we can use to invoke optimization - How
long it takes ?
2. What is the command line command to invo
We have 4 shards with 14GB index on each of them
Each shard has a master and 3 slaves(each of them with 32GB RAM)
We're expecting that the index size will grow to double or triple in near
future.
So we thought of merging our indexes to 28GB index so that each shard has
28GB index and also increase
Here's few list of queries
---
parallel zur xml beschreibungsdatei gibt es eine
die verbindung zwischen beiden sei ten geschieht
die owner klasse muss sich aus der
benutzer ein oder mehrere lieblingsfarben ausw hlen kann
found sample questions at http bjs ojp
1. So we have 24.5GB assigned to jvm which is half of the total memory, which
is 48GB RAM.(If that's what you meant, and if i am getting that right ?)
2. Size of *.fdt and *fdx is around 300m and 50m respectively.So that's
definitely less that 5%.
Do you see a problem there ?
Is there a way that w
It looks like reducing the jvm heap allocation did help in lowering the
response time to some extent.
Thanks for the pointer.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001056.html
Sent from the Solr - User mai
index hits == total number of documents found by search query.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001063.html
Sent from the Solr - User mailing list archive at Nabble.com.
Its 7.2Gig Hits. (GB was typo)
This is the total number of index hits - calculated by summing each
"numFound" attribute from solr query response.
We have RHEL Tikanga version.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp
Its 7,200,000 hits == number of documents found by all 10K queries.
We have RHEL tikanga version.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001069.html
Sent from the Solr - User mailing list archive at Nabble.
The queries were extracted from production log.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001182.html
Sent from the Solr - User mailing list archive at Nabble.com.
These are simple search queries and Its multithreaded .
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Index-linear-growth-Performance-degradation-tp4000934p4001184.html
Sent from the Solr - User mailing list archive at Nabble.com.
17 matches
Mail list logo