Hi,
first I'd like to thank those who've spent their time reading this,
especially Erick, Jason and Shawn. Thank you!
I've finally got it working. Shawn was right, I needed to enable updateLog
in solrconfig.xml and create the tlog directory. After doing, so I could
index documents sent on any nod
On 6/2/2014 2:21 PM, Marc Campeau wrote:
> I notice I have this in the logs when I start SOLR for default example (I
> had the same with my own connection)
>
> 21242 [coreZkRegister-1-thread-1] INFO
> org.apache.solr.cloud.ShardLeaderElectionContext – Enough replicas found
> to continue.
> 21242
I notice I have this in the logs when I start SOLR for default example (I
had the same with my own connection)
21242 [coreZkRegister-1-thread-1] INFO
org.apache.solr.cloud.ShardLeaderElectionContext – Enough replicas found
to continue.
21242 [coreZkRegister-1-thread-1] INFO
org.apache.solr.clou
Here's my solrconfig.xml:
4.4
${solr.data.dir:}
${solr.lock.type:native}
true
6
3
false
${solr.autoSoftCommit.maxTime:15000}
1024
bq: it's not getting replicated
This is definitely not what's expected. Are you by chance _configuring_
replication while at the same time using SolrCloud? Posting your
solrconfig.xml would help answer that.
This should be all that's in your solrconfig.xml file when running under
SolrCloud:
No
As of now I'm trying reindexing everything. Basically I have now an empty
collection and when I add a document it's not getting replicated. Not
trying anymore to load my old index anymore.
Marc
2014-05-30 16:44 GMT-04:00 Jason Hellman :
> Marc,
>
> Fundamentally it’s a good solution design to a
Marc,
Fundamentally it’s a good solution design to always be capable of reposting
(reindexing) your data to Solr. You are demonstrating a classic use case of
this, which is upgrade. Is there a critical reason why you are avoiding this
step?
Jason
On May 30, 2014, at 10:38 AM, Marc Campeau
2014-05-30 12:24 GMT-04:00 Erick Erickson :
> Let's back up a bit here. Why are you copying your indexes around?
> SolrCloud does all this for you. I suspect you've somehow made a mis-step.
>
I started by copying the index around because my 4.5.1 instance is not
setup as Cloud and I wanted to avo
Let's back up a bit here. Why are you copying your indexes around?
SolrCloud does all this for you. I suspect you've somehow made a mis-step.
So here's what I'd do by preference; Just set up a new collection and
re-index. Make sure all of the nodes are up and then just go ahead and
index to any of
Hi, forgot to mention that I'm migrating the index from Solr 4.5.1 to 4.8.1.
Thanks,
Marc Campeau
2014-05-30 9:54 GMT-04:00 Marc Campeau :
> Hi,
>
> I currently have a standalone SOLR 4.5.1deployment on an EC2 instance with
> a single collection and core containing an index that's roughly 10G.
10 matches
Mail list logo
