lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikhail Khludnev <>
Subject Why IndexFetcher commits after deleting obsolete index?
Date Fri, 08 Dec 2017 06:38:04 GMT
I mean this row

Sure, "New index in Master. Deleting mine..." makes sense. But committing
right after that is not really determined. Eg if this empty slave commit is
delayed it's assigned with late timestamp, and ignores master commit as

Don't you think it's a problem (at least for test stability)?

The possible solutions are
 - pass earler timestamp to commit explicitly, I'm not sure if it's ever
 - or always set skipCommitOnMasterVersionZero=true or by default at least.

More details at
Sincerely yours
Mikhail Khludnev

View raw message