I'm not sure what else to share here... I can try to code dive a bit
this week, but I imagine it is over my head and at a Lucene level.
Fortunately for us, re-indexing is not an issue, so we can manage it.
If someone can confirm it, I think it would be good to update the wiki
and let people know ev
On Fri, Jan 16, 2009 at 7:14 PM, Jacob Singh wrote:
> Hi Shalin,
>
> Sorry, my post was unlcear. I am calling snappull from the slave, I
> get that part, just obfuscating the domains incorrectly :). The
> problem it seems is the index version.
>
> The index was a 1.3 index and I've since moved t
Hi Shalin,
Sorry, my post was unlcear. I am calling snappull from the slave, I
get that part, just obfuscating the domains incorrectly :). The
problem it seems is the index version.
The index was a 1.3 index and I've since moved to 1.4. It's been
working great so far until I hit the replicatio
Hi Jacob,
You don't need to call snapshoot on the master. That is only used to create
a backup of the index files.
You are calling snappull on the master. It is only applicable for the
slaves. You don't need to issue these calls yourself at all. The
ReplicationHandler is designed to take care of
Hi Shalin,
Thanks for responding! This used to be a 1.3 index (could that be the issue?)
curl
'http://mydomain.com:8080/solr/065f079c24914a4103e2a57178164bbe//replication?command=indexversion'
Best,
Jacob
On Jan 15, 2009 3:32pm, Shalin Shekhar Mangar wrote:
> What is the output of /
What is the output of /replication?command=indexversion on the master?
On Fri, Jan 16, 2009 at 1:27 AM, Jacob Singh wrote:
> Hi folks,
>
> Here's what I've got going:
>
> Master Server with the following config:
>
>
>commit
>schema.xml,stopwords.txt,elevate.xml
>
>
>
>
Hi folks,
Here's what I've got going:
Master Server with the following config:
commit
schema.xml,stopwords.txt,elevate.xml
Slave server with the following:
http://mydomain:8080/solr/065f079c24914a4103e2a57178164bbe/replication
00:00:20
I
