Hi Guillaume,
thank you, glad this makes it easier.
Happy new year!
Sanne
On 2 January 2012 11:38, Guillaume Smet wrote:
> Hi Sanne and happy new year,
>
> On Fri, Dec 30, 2011 at 6:23 PM, Guillaume Smet
> wrote:
>> Let me setup our config to exclusive + native for the next few days.
>
> I can c
Hi Sanne and happy new year,
On Fri, Dec 30, 2011 at 6:23 PM, Guillaume Smet
wrote:
> Let me setup our config to exclusive + native for the next few days.
I can confirm you that using exclusive + native is OK for us and that
we don't have remaining locks anymore.
I concur it might be a sensible
On Fri, Dec 30, 2011 at 5:55 PM, Sanne Grinovero wrote:
> Proposal: https://github.com/hibernate/hibernate-search/pull/221
> could you see if it improves your experience with locks? I'm deploying
> a 4.1.0-SNAPSHOT as well.
Let me setup our config to exclusive + native for the next few days.
I'l
On 30 December 2011 16:03, Sanne Grinovero wrote:
[...]
> 3 - default to "native" locks in more cases. This "native" used to be
> troublesome on some OSes as documented by Lucene's javadoc, but I'm
> definitely implementing this one, as I just noticed this is no longer
> the case with latest vers
Hi Guillaume,
thanks, good observations and I share the idea to make it as easy as
possible out of the box, but I'm not sure about what is our best
option to provide that.
First, regarding your statement of considering older versions: the
locking options I've mentioned are not new in 4.0, so this
Hi Sanne,
On Fri, Dec 30, 2011 at 2:12 AM, Sanne Grinovero wrote:
> [very detailed explanation]
Thanks for taking the time to answer.
While I agree with you on most of what you explained, I think the
point is: is it a good default value?.
The typical development workflow of Debug mode / Play a
Hi,
a lock marker file is created any time an IndexWriter is opened, and
(should be) cleaned up when the IndexWriter is closed.
So if you kill the application without properly closing the
IndexWriter, this problem is expected and you'll have to cleanup the
lock file manually.
With "exclusive_index
On Wed, Dec 28, 2011 at 2:21 PM, Guillaume Smet
wrote:
> After our upgrade to 4.0 (from 3.4.1), we've started to have a lot of
> lock errors on our development boxes. I thought it was due to brutal
> kills of the JVM (typically Terminate in Eclipse) but we also have
> them in our CI environment on
Hi,
After our upgrade to 4.0 (from 3.4.1), we've started to have a lot of
lock errors on our development boxes. I thought it was due to brutal
kills of the JVM (typically Terminate in Eclipse) but we also have
them in our CI environment on a project where every test is OK.
The stracktraces look l
