Hoss Man created SOLR-4674:
------------------------------
Summary: repeaters must be configured to replicate on startup in
order to work properly when replicating config files
Key: SOLR-4674
URL: https://issues.apache.org/jira/browse/SOLR-4674
Project: Solr
Issue Type: Bug
Reporter: Mark Miller
Filing on Mark's behalf based on a mailing list thread about replication tests
related to automatic core reloads...
{quote}
Let's say you have 3 nodes, a master, a repeater, and a slave.
When you do updates and commit on the master, things will replicate to the
repeater. You now need to make the repeaters most replicatable commit the
latest commit, even though a normal trigger for this (startup, commit) has not
occurred. If you don't, the right stuff won't happen between the repeater and
the slave.
In the non core reload case, we currently reach right in the ReplicationHandler
and update the last replicatable commit point on the repeater as part of
installing the new index. This is somewhat new, there used to be a commit that
would push the slave gen past the leader by one.
In the Core reload case, it's a little trickier. If you are replicating on
startup, you should be fine - the right most replicatable commit will be set
when the core reloads. But if you don't, and just have replicate on commit, the
repeater won't be ready to replicate the right commit point to the slave.
I guess the best workaround for that at the moment is to be sure to have
replicate on startup set on your repeater.
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
