> Right you should never enable eviction on a cache used to store
> permanent data - like the Lucene index segment.

But couldn't you still have eviction if you used store to persist overflown 
data.

> How would you phrase the error message?

Well, at least put in the *right* cache name somewhere in the msg. ;-)
I though I was going blind, as requesting cache - the indexing one - clearly 
had NONE set as eviction strategy.

> On 22 November 2012 12:21, Ales Justin <ales.jus...@gmail.com> wrote:
>> Ah, OK, it should really be disabled on Lucene caches:
>> 
>>                <replicated-cache name="LuceneIndexesMetadata" mode="SYNC">
>>                    <transaction mode="NONE"/>
>>                    <eviction strategy="NONE"/>
>>                    <file-store preload="true" purge="false"/>
>>                </replicated-cache>
>>                <replicated-cache name="LuceneIndexesData" mode="SYNC">
>>                    <transaction mode="NONE"/>
>>                    <eviction strategy="NONE"/>
>>                    <file-store preload="true" purge="false"/>
>>                </replicated-cache>
>>                <replicated-cache name="LuceneIndexesLocking" mode="SYNC">
>>                    <transaction mode="NONE"/>
>>                    <eviction strategy="NONE"/>
>>                    <file-store preload="false" purge="true"/>
>>                </replicated-cache>
>> 
>> Horrible err msg ...
>> 
>> On Nov 22, 2012, at 12:53 PM, Ales Justin <ales.jus...@gmail.com> wrote:
>> 
>> I was changing cache config a bit, and got this:
>> * https://gist.github.com/4130728
>> 
>>   private static void verifyCacheHasNoEviction(AdvancedCache<?, ?> cache) {
>>      if (cache.getConfiguration().getEvictionStrategy().isEnabled())
>>         throw new IllegalArgumentException("DistributedSegmentReadLocker is
>> not reliable when using a cache with eviction enabled, disable eviction on
>> this cache instance");
>>   }
>> 
>> 
>> How do you then handle memory overflow on no-eviction caches?
>> 
>> 
>> -Ales
>> 
>> 
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev


_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev

Reply via email to