On Feb 27, 2013, at 10:51 AM, Michael Della Bitta <michael.della.bi...@appinions.com> wrote:
> Are there any temporary fixes to this problem aside from waiting for 4.2? Not really. I guess my advice would be this: If you use SolrCloud or single node, don't worry, this doesn't affect you. If you use 4.1 master->slave replication and you have not noticed this, I'd just wait for 4.2. There is not a lot you can do to work around it. You might ease up on how often you poll for changes if there is a problem. If you need something that doesn't replicate so often right now, 4.0 does not have the same issue. There might be the rare occasion it replicates when it does not need to, but it's not consistent as in 4.1. How did this happen? There was not a test to make sure it didn't happen and from a functionality point, it doesn't mess anything up for tests to detect. Because of that, other changes introduced this problem and it was not detected nor noticed by users until recently. I've added testing around it with the fixes for the future. - Mark
