Re: Atomic Update and stored copy-fields

2013-05-06 Thread raulgrande83
We have defined those copyfield destinations as stored because we have experienced some problems when highlighting in them. These fields have different Tokenizers and Analyzers. We have found that if we search in one of them but highlight in a different one some words that doesn't match the first q

Atomic Update and stored copy-fields

2013-04-26 Thread raulgrande83
Hello everybody, We are using last version of Solr (4.2.1) and making some tests on Atomic Updates. The Solr wiki says that: /(...) requires that all fields in your SchemaXml must be configured as stored="true" except for fields which are destinations -- which must be configured as stored="false

Out of Memory doing a query Solr 4.2

2013-03-14 Thread raulgrande83
Hi After doing a query to Solr to get the uniqueIds (string of 20 characters) of 700 documents in a collection, I'm getting an out of memory error using Solr 4.2. I tried to increase the JVM-Memory 1G (from 3G to 4G) however this didn't change anything. This was working on 3.5. I've moved from

Re: Slaves always replicate entire index & Index versions

2013-02-27 Thread raulgrande83
I always have a "clean" index folder, I mean I don't get the index. folder at any time. Besides, I haven't noticed that slaves pull entire index in replication. I restarted my repeater node and replication started to work fine again, the slaves updated all the changes that their master had. But af

Re: Slaves always replicate entire index & Index versions

2013-02-26 Thread raulgrande83
I'm now having a different problem. In my master-repeater-2slaves architecture I have these generations versions: Master: 29147 Repeater: 29147 Slaves: 29037 When I go to slaves logs it shows "Slave in sync with master". That is apparently because if I do http://localhost:17045/solr/replication?co

Re: Slaves always replicate entire index & Index versions

2013-02-25 Thread raulgrande83
Hello everybody. I have downloaded the 4.2-SNAPSHOT version that Mark linked at the JIRA and our first tests have been OK. Slaves now doesn't need to replicate the entire index and index versions between nodes are the same when replication process is completed. This 4.2 version is here: https://i

Re: Slaves always replicate entire index & Index versions

2013-02-22 Thread raulgrande83
Amit Nithian wrote > For your issue above in your last post, is it possible that there was a > commit on the master in that slight window after solr checks for the > latest > generation of the master but before it downloads the actual files? How > frequent are the commits on your master? No, I don

Re: Slaves always replicate entire index & Index versions

2013-02-21 Thread raulgrande83
Thanks for the patch, we'll try to install these fixes and post if replication works or not. I renamed 'index.' folders to just 'index' but it didn't work. These lines appeared in the log: INFO: Master's generation: 64594 21-feb-2013 10:42:00 org.apache.solr.handler.SnapPuller fetchLatestIndex I

Re: Slaves always replicate entire index & Index versions

2013-02-21 Thread raulgrande83
Hi Amit, I have came across some JIRAs that may be useful in this issue: https://issues.apache.org/jira/browse/SOLR-4471 https://issues.apache.org/jira/browse/SOLR-4354 https://issues.apache.org/jira/browse/SOLR-4303 https://issues.apache.org/jira/browse/SOLR-4413 https://issues.apache.org/jira/br