[
https://issues.apache.org/jira/browse/SOLR-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3176:
---------------------------
Fix Version/s: (was: 4.0)
removing fixVersion=4.0 since there is no evidence that anyone is currently
working on this issue. (this can certainly be revisited if volunteers step
forward)
Note also: i'm not sure this issue is even a good idea anymore, as
ReplicationHandler is now also used for SolrCloud, where it doesn't have to be
explicitly configured as either a master or a slave. The current 4x example
solrconfig includes a ReplicationHandler that looks like this...
{code}
<requestHandler name="/replication" class="solr.ReplicationHandler" >
<!--
To enable simple master/slave replication, uncomment one of the
sections below, depending on wether this solr instance should be
the "master" or a "slave". If this instance is a "slave" you will
also need to fill in the masterUrl to point to a real machine.
-->
<!--
<lst name="master">
<str name="replicateAfter">commit</str>
<str name="replicateAfter">startup</str>
<str name="confFiles">schema.xml,stopwords.txt</str>
</lst>
-->
<!--
<lst name="slave">
<str name="masterUrl">http://your-master-hostname:8983/solr</str>
<str name="pollInterval">00:00:60</str>
</lst>
-->
</requestHandler>
{code}
I would think that at a minimum, any logic for disabling replication if there
is no master/slave config should only do so if we are not in "ZooKeeperMode"
> If replicationHandler has both <master> and <slave> sections disabled
> (enable=false) it should disable itself
> -------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3176
> URL: https://issues.apache.org/jira/browse/SOLR-3176
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 3.5
> Reporter: Jan Høydahl
> Attachments: SOLR-3176.patch
>
>
> Today ReplicationHandler silently starts up, but when a slave tries to pull
> indexversion the (wrongly configured) master answers "0" instead of not
> answering at all which would be a better response.
> Also, it should log a warning that ReplicationHandler is enabled but has no
> active master or slave section, and then disable the handler altogether.
--
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]
