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

Manik Surtani manik at jboss.org
Mon Jul 13 17:59:19 EDT 2009

On 13 Jul 2009, at 17:10, Łukasz Moreń wrote:

> 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 names.
> Are there any Infinispan drawbacks to have a high number of caches  
> in the network? Sharing JGroups channels can help in that?

They already share JGroups channels and other "heavy" components  
wherever possible.  Its just that configuration becomes more of a  
pain, etc.

When you say one cache per index, how do you define an index?  Does 1  
index mean all indexed data for a single java type?  In which case  
couldn't these scale up dynamically and potentially on-demand?  No  
wait - these are fixed in Hibernate Search on startup, correct?

Manik Surtani
manik at jboss.org
Lead, Infinispan
Lead, JBoss Cache

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-dev/attachments/20090713/bdfab041/attachment.html 

More information about the hibernate-dev mailing list