After upgrading a project to 7.2.2 I've noticed that the indexes write.lock file is not removed after the indexing occurrs. It doesn't seem to get removed until the site is restarted and/or the application pool is recycled.
we are experiencing the same problems on a few sites (every site was upgraded from previous version to 7.2.4). before the upgrade, we didn't experience any problems.
Hi Andreas,
I created a ticket on the Umbraco bug tracker, and Shannon Deminick explained that they "now keep the lucene writer open while the app is running for performance reasons", and the behaviour is as expected.
So yeah, it's not a bug, it just works a little differently to how it used to.
thx for the information. I think we have found our Problem, looks like an faulty Microsoft Update that causes our file locks and app pool recyclings. More Info here.
Examine write.lock persisting after upgrading to 7.2.2
After upgrading a project to 7.2.2 I've noticed that the indexes write.lock file is not removed after the indexing occurrs. It doesn't seem to get removed until the site is restarted and/or the application pool is recycled.
Is anyone else experiencing this using 7.2.2?
Hi,
we are experiencing the same problems on a few sites (every site was upgraded from previous version to 7.2.4). before the upgrade, we didn't experience any problems.
did you solve your problem?
Cheers,
Andreas
Hi Andreas, I created a ticket on the Umbraco bug tracker, and Shannon Deminick explained that they "now keep the lucene writer open while the app is running for performance reasons", and the behaviour is as expected.
So yeah, it's not a bug, it just works a little differently to how it used to.
You can read Shannon's full response here.
Hi,
thx for the information. I think we have found our Problem, looks like an faulty Microsoft Update that causes our file locks and app pool recyclings. More Info here.
Cheers
is working on a reply...