Hi
We have actually tested this and found that the following will do it
* Shutdown all Solr nodes - make sure ZKs are still running
* For each replica (shard-instance) move its data-folder to the new
server (if they are not already available to it through some shared storage)
* For each repilca
On 1/26/2013 12:55 AM, Rahul Bishnoi wrote:
Thanks for quick reply and addressing each point queried.
Additional asked information is mentioned below:
OS = Ubuntu 12.04 (64 bit)
Sun Java 7 (64 bit)
Total RAM = 8GB
SolrConfig.xml is available at http://pastebin.com/SEFxkw2R
Rahul,
The MaxPe
On 1/26/2013 6:31 AM, Per Steffensen wrote:
We have actually tested this and found that the following will do it
* Shutdown all Solr nodes - make sure ZKs are still running
* For each replica (shard-instance) move its data-folder to the new
server (if they are not already available to it through
Hey Shawn - got a suggestion for an addition for the wiki that would
have saved you some time here?
- Mark
On Sat, Jan 26, 2013 at 1:22 PM, Shawn Heisey wrote:
> On 1/26/2013 6:31 AM, Per Steffensen wrote:
>>
>> We have actually tested this and found that the following will do it
>> * Shutdown a
Is there any chance that you were experimenting with an ngram filter for the
field? If you were, and merely changed the field type without reindexing,
this behavior makes sense. In other words, you appear to have had some
filter that broke words into one and two-character terms.
Separate from
Hi Guys,
We are using Solr 4.0 in a 2 shard cluster with replication enabled. On
solr startup we get an exception like this:
WARNING: Could not getStatistics on info bean
org.apache.solr.handler.ReplicationHandler
java.lang.IllegalArgumentException: ./collectionOne_shard2_1/data/index
does not exi
On 1/26/2013 11:37 AM, Mark Miller wrote:
Hey Shawn - got a suggestion for an addition for the wiki that would
have saved you some time here?
I have updated the SolrCloud wiki page. I put a small note under
Getting Started that references the meat of my addition under Parameter
Reference. D
On 1/26/2013 11:50 AM, Alexandre Rafalovitch wrote:
Hello,
I just upgraded to 4.1 and my 4.0 multicore setup immediately stopped
booting. I fixed apache-* prefix changes, but have another one that is more
weird.
Basically, I have two cores with lib sections in their solrconfig.xml
(running from
Thanks for workaround Shawn.
This is for a set of example (in a book), so the cores are rather different
from each other as a libraries. Also, I want clearest possible explanation.
But it is good to know the other options.
Regards,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedIn:
I am seeing the following exception very occasionally while indexing a large
collection using Solr 4.1:
Jan 26, 2013 9:09:19 AM org.apache.solr.core.CachingDirectoryFactory close
INFO: Releasing directory:/ssd/solr
Jan 26, 2013 9:09:19 AM org.apache.solr.update.DirectUpdateHandler2 commit
INFO: e
Solr has an autocomplete/suggester feature:
http://wiki.apache.org/solr/Suggester
-- Jack Krupansky
-Original Message-
From: ilay
Sent: Thursday, January 24, 2013 7:34 AM
To: solr-user@lucene.apache.org
Subject: Solr autocomplete feature
Hi
I want to change autocomplete implementati
Hi,
Actually Mark Miller replied to this issue and it seems to be fixed in Solr
4.1 as far as I checked. Anyway, it was harmless both for querying and
indexing.
Regards.
On 26 January 2013 20:14, Prashant Saraswat wrote:
> Hi Guys,
>
> We are using Solr 4.0 in a 2 shard cluster with replicatio
I use HttpSolrServer (going through an external loadbalancer) to connect to my
solrCloud. When I try to index an object via httpSolrServer.addBean(), I get a
400 error back and in the SolrCloud node, I see the following exception:
SEVERE: org.apache.solr.common.SolrException: Unsupported Conten
The rule you quoted is not relevant to your two example queries since they
both have at least one "MUST" ("+") term.
I'll restate the rule: If there are one or more MUST clauses, then none of
the SHOULD clauses need be present for a document to be a match, but if
there are no MUST clauses, the
My bad…turns out that I was using the HttpSolrServer in 3.6.1 in my client
side. When I changed it to CommonsHttpSolrServer in 3.6.1 or HttpSolrServer in
4.1, everything works correctly.
On Jan 26, 2013, at 4:18 PM, santoash wrote:
> I use HttpSolrServer (going through an external loadbalanc
Thanks Erik.
Will take your advice as a long term solution. Currently working around by
using the the regex capability added in parsing the 'fl' parameter, using
'fl=E_*'
On Wed, Jan 9, 2013 at 6:07 AM, Erick Erickson wrote:
> You really have a field name with '@' symbols in it? If it worked in
16 matches
Mail list logo