[
https://issues.apache.org/jira/browse/SOLR-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885556#comment-13885556
]
Vitaliy Zhovtyuk commented on SOLR-5589:
----------------------------------------
Lets consider the following config:
<requestHandler name="/replication" class="solr.ReplicationHandler" >
<lst name="master">
<str name="replicateAfter">commit</str>
<str name="confFiles">schema.xml</str>
</lst>
<lst name="slave">
<str name="enable">false</str>
<str name="masterUrl">http://127.0.0.1:TEST_PORT/solr</str>
<str name="pollInterval">00:00:01</str>
<str name="compression">COMPRESSION</str>
</lst>
</requestHandler>
Slave is disabled, but master can be used to replicate to separate Solr
instance.
Therefore i think it's only make sense to disable replication when both master
and slave explicitly disabled.
And i think it will not have side effects with replication when slave is
disabled for some reason, but master is replication to separate instance.
> Disabled replication in config is ignored
> -----------------------------------------
>
> Key: SOLR-5589
> URL: https://issues.apache.org/jira/browse/SOLR-5589
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 4.5
> Reporter: alexey
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.7
>
> Attachments: SOLR-5589.patch, SOLR-5589.patch, SOLR-5589.patch,
> SOLR-5589.patch
>
>
> When replication on master node is explicitly disabled in config, it is still
> enabled after start. This is because when both master and slave
> configurations are written with enabled=false, replication handler considers
> this node is a master and enables it. With proposed patch handler will
> consider this as master node but will disable replication on startup if it is
> disabled in config (equivalent to disablereplication command).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
