You _could_ configure it as a slave, if you plan to sometimes use it as
a slave. It can be configured as both a master and a slave. You can
configure it as a slave, but turn off automatic polling. And then issue
one-off replicate commands whenever you want.
But yeah, it gets messy, your use case is definitely not what
ReplicationHandler is expecting, definitely some Java improvements would
be nice, agreed.
On 6/1/2011 12:20 PM, Upayavira wrote:
On Wed, 01 Jun 2011 11:47 -0400, "Jonathan Rochkind"<rochk...@jhu.edu>
wrote:
On 6/1/2011 11:26 AM, Upayavira wrote:
Probably the ReplicationHandler would need a 'one-off' replication
command...
It's got one already, if you mean a command you can issue to a slave to
tell it to pull replication right now. The thing is, you can only issue
this command if the core is configured as a slave. You can turn off
polling though.
You can include a custom masterURL in the one-off pull command, which
over-rides whatever masterURL is configured in the core --- but you
still need a masterURL configured in the core, or Solr will complain on
startup if the core is configured as slave without a masterURL. (And if
it's not configured as a slave, you can't issue the one-off pull
command).
Right, but this wouldn't be a slave - so I'd want to wire the
destination core so that it can accept a 'pull request' without being
correctly configured. Stuff to look at.
Upayavira
