Hi,<br><br>I'm wondering if it is reasonable to have multiple threads/nodes that modifies indexes in Lucene Directory based on Infinispan? Let's assume that two nodes try to update index in this same time. First one creates IndexWriter and obtains <br>
write lock. There is high propability that second node throws LockObtainFailedException (as one IndexWriter is allowed on single index) and index is not modified. How is that? Should be always only one node that makes changes in <br>
the index?<br><br>Cheers,<br>Lukasz<br><br><div class="gmail_quote">W dniu 15 września 2009 01:39 użytkownik Łukasz Moreń <span dir="ltr"><<a href="mailto:lukasz.moren@gmail.com">lukasz.moren@gmail.com</a>></span> napisał:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi, <br><br>With using JMeter I wanted to check if Infinispan dir does not crash
under heavy load in "real" use and check performance in comparison with none/other
directories.<br>
However appeared problem when multiple IndexWriters tries to modify
index (test InfinispanDirectoryTest) - random deadlocks, and Lucene
exceptions.<br>
IndexWriter tries to access files in index that were removed before. I'm looking into it, but not having good idea. <br>
<br>Concerning the last part, I think similar thing is done in
InfinispanDirectoryProviderTest. Many threads are making changes and
searching (not checking if db is in sync with index).<br>
If threads finish their work, with Lucene query I'm checking if index contains as many results as expected. Maybe you meant something else?<br>
Would be good to run each node in different VM.<div class="im"><br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">Great ! Looking forward to it. What state are things in at the moment<br>
if I want to play around with it ?<br></blockquote></div><div><br>Should work with with one master(updates index) and one many slave nodes (sends changes to master). I tried with one master and one slave (both with jms and jgroups backend) and worked ok. Still fails if multiple nodes want to modify index.<br>
</div>
<br>I've attached patch with current version.<br><br>
Cheers,<br>
Łukasz<br><br><div class="gmail_quote">2009/9/13 Michael Neale <span dir="ltr"><<a href="mailto:michael.neale@gmail.com" target="_blank">michael.neale@gmail.com</a>></span><div><div></div><div class="h5"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Great ! Looking forward to it. What state are things in at the moment<br>
if I want to play around with it ?<br>
<br>
Sent from my phone.<br>
<br>
On 13/09/2009, at 7:26 PM, Sanne Grinovero <<a href="mailto:sanne.grinovero@gmail.com" target="_blank">sanne.grinovero@gmail.com</a>><br>
wrote:<br>
<div><div></div><div><br>
> 2009/9/12 Michael Neale <<a href="mailto:michael.neale@gmail.com" target="_blank">michael.neale@gmail.com</a>>:<br>
>> That does sounds pretty cool. Would be nice if the lucene indexes<br>
>> could scale along with how people will want to use infinispan.<br>
>> Probably worth playing with.<br>
><br>
> Sure, this is the goal of Łukasz's work; We know compass has<br>
> some good Directories, but we're building our own as one based<br>
> on Infinispan is not yet available.<br>
><br>
>><br>
>> Sent from my phone.<br>
>><br>
>> On 13/09/2009, at 8:37 AM, Jeff Ramsdale <<a href="mailto:jeff.ramsdale@gmail.com" target="_blank">jeff.ramsdale@gmail.com</a>><br>
>> wrote:<br>
>><br>
>>> I'm afraid I haven't followed the Infinispan-Lucene implementation<br>
>>> closely, but have you looked at the Compass Project?<br>
>>> (<a href="http://www.compass-project.org/overview.html" target="_blank">http://www.compass-project.org/overview.html</a>) It provides a<br>
>>> simplified interface to Lucene (optional) as well as Directory<br>
>>> implementations built on Terracotta, Gigaspaces and Coherence. The<br>
>>> latter, in particular, might be a useful guide for the Infinispan<br>
>>> implementation. I believe it's mature enough to have solved many of<br>
>>> the most difficult problems of implementing Directory on a<br>
>>> distributed<br>
>>> Map.<br>
>>><br>
>>> If someone has any experience with Compass (particularly it's<br>
>>> Directory implementations) I'd be interested in hearing about it...<br>
>>> It's Apache 2.0 licensed, btw.<br>
>>><br>
>>> -jeff<br>
>>> _______________________________________________<br>
>>> infinispan-dev mailing list<br>
>>> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>><br>
><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></div></div></blockquote></div></div></div><br>
</blockquote></div><br>