lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antony Stubbs (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3034) replicateAfter optimize not working
Date Wed, 01 Feb 2012 16:36:58 GMT


Antony Stubbs commented on SOLR-3034:

Yes, replication is working great after new imports.

Should optimising cause the index generation to increment? I don't see it increment. After
clicking optimise, I only see log messages around the commit, nothing about optimise.

Also, in the UI, after I run optimise, the tick appears, but if I refresh the page, it does
not appear to remain 'optimised', as the tick goes back to cross. (There are no imports happening).

I'm running on a build from jenkins from

Perhaps my index isn't actually being optimised..

> replicateAfter optimize not working
> -----------------------------------
>                 Key: SOLR-3034
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message