I think you may need to tell the replication handler to enable
replication after startup too?
<str name="replicateAfter">commit</str>
<str name="replicateAfter">startup</str>
-Yonik
http://www.lucidimagination.com
On Fri, Oct 16, 2009 at 12:58 PM, Jérôme Etévé <jerome.et...@gmail.com> wrote:
> Hi All,
> I'm facing a small problem with the replication handler:
>
> After restarting my master container (tomcat),
> /admin/replication/index.jsp shows me the right information,
> basically the same indexversion as before the restart (no
> commits/optimize have been done after restart):
>
> Local Index Index Version: 1255709893043, Generation: 8
>
> However, if I query the handler with the filelist command and this
> version number :
> /replication?command=filelist&indexversion=1255709893043 , the handler
> gives me an error:
>
> <str name="status">invalid indexversion</str>
>
> So I think my slaves will get confused if this information doesn't
> remain consistent after a master container restart.
>
> Is there a way to go around this problem, for instance by triggering a
> commit on startup (or reload) ?
>
>
> Thanks!
>
> Jerome.
>
> --
> Jerome Eteve.
> http://www.eteve.net
> jer...@eteve.net
>
