[infinispan-issues] [JBoss JIRA] (ISPN-4584) Stricter validation of cache configurations for distributed indexes

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004010#comment-13004010 ] 

Sanne Grinovero commented on ISPN-4584:
---------------------------------------

{quote}Another check that would be useful is that the triple locking/metadata/data caches is not shared, e.g cache indexedA using lockingA, metadataA and dataA, while cache indexedB uses lockingA, metadataA and dataA - I've accidentally configured it that way (as in my test only indexedB should have been used) and stumbled again on ISPN-4577.{quote}
Good point, if we don't accept that configuration we should validate against it. 
Although, there is the use case in which people actually want to share the same index across Caches or even applications; a better solution however would be to finish the CacheManager level Query Engine, so that different caches can actually forward work to the same IndexWriter rather than locking each other out.

But I agree, if we don't do that timely we should validate this.

> Stricter validation of cache configurations for distributed indexes
> -------------------------------------------------------------------
>
>                 Key: ISPN-4584
>                 URL: https://issues.jboss.org/browse/ISPN-4584
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Lucene Directory
>            Reporter: Sanne Grinovero
>            Assignee: Gustavo Fernandes
>            Priority: Minor
>
> See also ISPN-4577 : it should not be allowed to configure a distributed metadata cache while the chunks cache is using local mode.
> Ideally think of additional strict checks which we should apply.. suggestions?
> Mitigated by ISPN-4340



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)