[hibernate-dev] Re: [infinispan-dev] Hibernate Search alternative Directory distribution

Łukasz Moreń lukasz.moren at gmail.com
Mon Jul 13 12:10:52 EDT 2009

> 1. share the same grid cache between the master and the slaves

Infinispan has a flat structure. The key has to contain:

 - the index name

 - the chunk name

Both with essentially be the unique identifier.

I suppose in this idea all indexes are stored in a one single grid. What
about one Infinispan grid per directory, similarly to RAMDirectory or
FSDirectory? IMHO it could make some simplifications i.e. in metadata or key
Are there any Infinispan drawbacks to have a high number of caches in the
network? Sharing JGroups channels can help in that?


2009/7/9 Emmanuel Bernard <emmanuel at hibernate.org>

> On  Jul 9, 2009, at 16:16, Manik Surtani wrote:
>>> In the case of replication, make sure a FD back end can be activated in
>>> case the grid goes to the unreachable clouds of total inactivity.
>> FD backend?  I presume you mean a cache store.  Have a look at the
>> different cache stores we ship with, I reckon a FileCacheStore would do the
>> trick for you.
>> http://infinispan.sourceforge.net/4.0/apidocs/org/infinispan/loaders/CacheStore.html
>> http://infinispan.sourceforge.net/4.0/apidocs/org/infinispan/loaders/file/FileCacheStore.html
> Yes I meant FS as FileSystem, but any backend would do (though DB would be
> a bad choice).
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-dev/attachments/20090713/a4d5fba0/attachment.html 

More information about the hibernate-dev mailing list