Now, every directory provider creates new Infinispan CacheManager - factory for caches. Each manager creates cache with defined name. Caches with this same name make distributed one, so we can have one common cache, cache per directory, depends how they are named - that way cache is shared. This is really not efficient since heavy CacheManager is created with every indexed entity - ideally one per VM.<div>
The better idea I think is to share one CacheManager between all directories in node. Then shared are also caches objects locally - not like previously every time is created new one. </div><div>HSearch started twice, independently, that both instances don't share resources - directories.? E.g. every time with different configuration? </div>
<div>To achieve that can be either created new CacheManager every HS start, or used one, but with different cache names per app.</div><div> </div><div><br></div><div><div class="gmail_quote">2009/8/14 Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word">How do you share the cache between different directories? <div>A static field would not work well as it would prevent HSearch to be started twice in a single app.</div>
<div><br></div><div>Anyway if we share the cache, I would still like to use the per directory provider configuration strategy (from a config property point of view) and raise an exception if it turns out the Infinispan cache config is different between two different indexes. That way we can improve down the road.</div>
<div><div></div><div class="h5"><div><br><div><div>On 14 août 09, at 05:33, Łukasz Moreń wrote:</div><br><blockquote type="cite">There is one cache for all indexes. In this case scoping configuration will be hard.<div>Yes, some default config will be provided. Right, different propterties for xml and programmatic would be better.</div>
<div><br><div class="gmail_quote"> 2009/8/14 Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Question,<br> Do we have one cache for all indexes (directories) or one per directory?<br> <br> I feels wrong to see this configuration not scoped per index<br> hibernate.search.default.directory_provider blah.blah.InfinispanDirectoryProvider<br>
hibernate.search.default.infinispan_conf com.acme.CacheFactoryImpl<br> <br> hibernate.search.Address.directory_provider blah.blah.InfinispanDirectoryProvider<br> hibernate.search.Address.infinispan_conf conf.xml<br> <br>
hibernate.search.User.directory_provider blah.blah.InfinispanDirectoryProvider<br> hibernate.search.User.infinispan_conf auto<br> <br> As Sanne pointed out, maybe we want different properties for XML, programmatic and built-in configs. I kinda like the idea of one config but it seems it will be hard to differenciate a class from a config file.<br>
<font color="#888888"> <br> Emmanuel</font><div><div></div><div><br> <br> On 13 août 09, at 18:33, Łukasz Moreń wrote:<br> <br> </div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div> I was thinking that maybe we can expose full conf options. Infinispan supports programmatical and xml ways to configure cache.<br> To achieve first one, could be created some interface with factory method that returns cache. User can implement that and create cache as he wants.<br>
<br> Something like that:<br> <br> <property name="hibernate.search.infinispan.conf" value="org.hibernate.search.store.infinispan.CacheFactoryImpl" /><br> <br> and for xml<br> <br> <property name="hibernate.search.infinispan.conf" value="xml-conf.xml" /><br>
<br> <br> Exposing some configuration to infinispan makes sense. can you start a thread explainig what is configurable and which one you think we should expose to hsearch users. Ideally I would like to offer one or two defaut config scenarios and allow to fallback to a custom config.<br>
<br> Cheers,<br> Lukasz Moren<br></div></div><div> _______________________________________________<br> hibernate-dev mailing list<br> <a href="mailto:hibernate-dev@lists.jboss.org" target="_blank">hibernate-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hibernate-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/hibernate-dev</a><br> </div></blockquote> <br> </blockquote></div><br></div></blockquote></div><br>
</div></div></div></div></blockquote></div><br></div>