I did optimize the master and the slave started replicating the indices!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replication-Problem-from-solr-3-6-to-solr-4-0-tp4025028p4148953.html
Sent from the Solr - User mailing list archive at Nabble.com.
- Starting
replication process
11:17:30.713 [snapPuller-8-thread-1] ERROR o.a.s.h.SnapPuller - No files to
download for index generation: 87
Any solution/fix for it?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replication-Problem-from-solr-3-6-to-solr-4-0-tp4025028p4148703
is running solr 3.5
Would you be able to shed some light?
Thank you in advance!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replication-Problem-from-solr-3-6-to-solr-4-0-tp4025028p4121896.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Fri, Dec 20, 2013 at 1:33 PM, Mark Miller wrote:
> What Solr version?
I've seen the first problem in the thread with Solr 4.1, and the
second with both 4.1 and 4.6.
-Fred
--
Fred L. Drake, Jr.
"A storm broke loose in my mind." --Albert Einstein
What Solr version?
- Mark
On Dec 20, 2013, at 1:14 PM, Fred Drake wrote:
> Here's another sequence of messages I frequently see where replication
> isn't happening with no clearly identified cause:
>
> INFO org.apache.solr.handler.SnapPuller; Starting replication process
> INFO org.apache.so
Here's another sequence of messages I frequently see where replication
isn't happening with no clearly identified cause:
INFO org.apache.solr.handler.SnapPuller; Starting replication process
INFO org.apache.solr.handler.SnapPuller; Master's generation: 6
INFO org.apache.solr.handler.SnapPuller;
I have a multi-core master/slave configuration that's showing
unexpected replication behavior for one core; other cores are
replicating without problems.
The master is running Solr 4.1; one slave is running 4.1 under Tomcat,
and another (for testing) is running 4.6 under Jetty. These are
exhibiti
In that case, I'm kind of stuck. You've already rebuilt your index
from scratch and removed it from your slaves. That should have
cleared out most everything that could be an issue. I'd suggest
you set up a pair of machines from scratch and try to set up an
index/replication with your current schem
Hi Erick,
It's not possible because both master and slaves using same binaries.
Thanks...
On Fri, Mar 23, 2012 at 5:30 PM, Erick Erickson wrote:
> Hmmm, looking at your stack trace in a bit more detail, this is really
> suspicious:
>
> Caused by: org.apache.lucene.index.IndexFormatTooNewExcept
Hmmm, looking at your stack trace in a bit more detail, this is really
suspicious:
Caused by: org.apache.lucene.index.IndexFormatTooNewException: Format
version is not supported in file 'segments_1': -12 (needs to be between -9
and -11)
This *looks* like your Solr version on your slave is older t
Hi Erick,
I've already tried step 2 and 3 but it didn't help. It's almost impossible
to do step 1 for us because of project dead-line.
Do you have any other suggestion?
Thank your reply.
On Fri, Mar 23, 2012 at 4:56 PM, Erick Erickson wrote:
> Hmmm, that is odd. But a trunk build from that lon
Hmmm, that is odd. But a trunk build from that long ago is going
to be almost impossible to debug/fix. The problem with working
from trunk is that this kind of problem won't get much attention.
I have three suggestions:
1> update to current trunk. NOTE: you'll have to completely
reindex your
Hi everyone,
We are using very early version of Solr 4.0 and we've some replication
problems. Actually we used this build more than one year without any
problem but when I made some changes on schema.xml, the following problem
started.
I've just changed schema.xml with adding multiValued="true" a
Hello!
Thanks for the answer Shawn.
--
Regards,
Rafał Kuć
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> On 2/6/2012 3:04 AM, Rafał Kuć wrote:
>> Hello!
>>
>> We have Solr running on Windows. Once in a while we see a problem with
>> replication failing. While slave server replic
On 2/6/2012 3:04 AM, Rafał Kuć wrote:
Hello!
We have Solr running on Windows. Once in a while we see a problem with
replication failing. While slave server replicates the index, it throws
exception like the following:
SEVERE: Unable to copy index file from:
D:\web\solr\collection\data\index.20
Hello!
We have Solr running on Windows. Once in a while we see a problem with
replication failing. While slave server replicates the index, it throws
exception like the following:
SEVERE: Unable to copy index file from:
D:\web\solr\collection\data\index.2011102510\_3s.fdt
to: D:\web\solr\Col
Hello List,
What's wrong with my replication?
One of my slaves logs this from time to time.
The slave runs on 3.1.0.
20.06.2011 12:31:32 org.apache.solr.common.SolrException log
SCHWERWIEGEND: ClientAbortException: java.io.IOException
at
org.apache.catalina.connector.OutputBuffer.realWr
did you double check
http://machine:port/solr/website/admin/replication/ to see the
"master" is indeed a master?
On Mon, Dec 13, 2010 at 1:01 PM, Ralf Mattes wrote:
> On Mon, 13 Dec 2010 12:31:27 -0500, Xin Li wrote:
>
>> " indexversion returned by the indexversion command is 0 while the same
>>
On Mon, 13 Dec 2010 12:31:27 -0500, Xin Li wrote:
> " indexversion returned by the indexversion command is 0 while the same
> information from the details command is 292192351652 ..."
>
> This only happens to a Slave machine. For a Master machine, indexversion
> returns the same number as details
" indexversion returned by the indexversion command is 0 while the
same information from the details command is 292192351652 ..."
This only happens to a Slave machine. For a Master machine,
indexversion returns the same number as details command.
On Mon, Dec 13, 2010 at 11:06 AM, Ralf Mattes
Hello list,
I'm trying to set up a replicating solr system (one master, one slave) here.
Everything _looks_ o.k. but replication fails. A little debugging shows the
following:
r...@slave:~# curl
'http://master:8180/solr/website/replication?command=indexversion&wt=json' &&
echo ''
{"responseH
Multiple replicateAfter for example: startup,optimize I believe this
was causing the issue, I limited it to commit, and it started to work
(with no other changes to solrconfig.xml)
On Tue, Jan 12, 2010 at 11:24 AM, Yonik Seeley
wrote:
> On Tue, Jan 12, 2010 at 2:17 PM, Jason Rutherglen
> wrote:
On Tue, Jan 12, 2010 at 2:17 PM, Jason Rutherglen
wrote:
> It was having multiple replicateAfter values... Perhaps a bug, though
> I probably won't spend time investigating the why right now, nor
> reproducing in the test cases.
Do you mean that you changed the config and now it's working?
We hav
It was having multiple replicateAfter values... Perhaps a bug, though
I probably won't spend time investigating the why right now, nor
reproducing in the test cases.
On Tue, Jan 12, 2010 at 11:10 AM, Jason Rutherglen
wrote:
> Hmm...Even with the IP address in the master URL on the slave, the
> in
Hmm...Even with the IP address in the master URL on the slave, the
indexversion command to the master mysteriously doesn't show the
latest commit... Totally freakin' bizarre!
On Tue, Jan 12, 2010 at 10:53 AM, Jason Rutherglen
wrote:
> There's a connect exception on the client, however I'd expect
There's a connect exception on the client, however I'd expect this to
show up in the slave replication console (it's not). Is this correct
behavior (i.e. not showing replication errors)?
On Mon, Jan 11, 2010 at 9:50 AM, Jason Rutherglen
wrote:
> Yonik,
>
> I added startup to replicateAfter, howe
Yonik,
I added startup to replicateAfter, however no dice... There's no
errors the Tomcat log.
The output of:
http://localhost-master:8080/solr/main/replication?command=indexversion
0
0
0
0
The master replication UI:
Local Index Index Version: 1263182366335, Generation: 3
Locati
Did you try adding "startup" to the list of events to replicate after?
-Yonik
http://www.lucidimagination.com
On Mon, Jan 11, 2010 at 12:25 PM, Jason Rutherglen
wrote:
> Hi, sorry for the somewhat inane question:
>
> I setup replication request handler on the master however I'm not
> seeing any
Hi, sorry for the somewhat inane question:
I setup replication request handler on the master however I'm not
seeing any replicatable indexes via
http://localhost:8080/solr/main/replication?command=indexversion
Queries such as *:* yield results on the master (so I assume the
commit worked). The re
29 matches
Mail list logo
