[
https://issues.apache.org/jira/browse/SOLR-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197119#comment-13197119
]
Hoss Man commented on SOLR-3034:
--------------------------------
FWIW: replicateAfter=commit is a super set of replicateAfter=optimize because
every optimize command is also a commit commant ... if you are replicating
after every commit then you are automatically replicating after every optimize.
that's the reason the UI only shows "commit, startup", it's "deduping" the
list.
However: that wouldn't explain why you aren't seeing replication happen after
an optimize. Are you seeing replication happen at all?
I just tried a quick sanity check using trunk r1237878 with the example
modified to act as a master with replicateAfter commit & optimize and i was
definitely seeing http://localhost:8983/solr/replication?command=indexversion
return a new indexversion after every commit or optimize.
when i changed the config to *only* use replicateAfter=optimize, then
indexversion would return a new version after every optimize command, but not
after every commit
...so things are working exactly as expected on the master side from what i can
see.
> replicateAfter optimize not working
> -----------------------------------
>
> Key: SOLR-3034
> URL: https://issues.apache.org/jira/browse/SOLR-3034
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Antony Stubbs
>
> I have:
> {noformat}
> <str name="replicateAfter">optimize</str>
> <str name="replicateAfter">commit</str>
> <str name="replicateAfter">startup</str>
> {noformat}
> But the UI only shows:
> {noformat}
> replicateAfter:commit, startup
> {noformat}
> And sure enough, optimizing does not cause a replication to happen.
> Also, replicating an optimized index, does not seem to keep in "optimized" on
> the slave. Is that really the case, or is it a bug? I would expect if an
> index is optimized on master, when it is then replicated to slaves, the
> slaves would receive the optimized index.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
