[infinispan-issues] [JBoss JIRA] Created: (ISPN-909) Segments locked during merge

Tristan Tarrant (JIRA) jira-events at lists.jboss.org
Tue Feb 1 05:42:39 EST 2011


Segments locked during merge
----------------------------

                 Key: ISPN-909
                 URL: https://issues.jboss.org/browse/ISPN-909
             Project: Infinispan
          Issue Type: Bug
          Components: Lucene Directory
    Affects Versions: 4.2.0.Final
            Reporter: Tristan Tarrant
            Assignee: Sanne Grinovero
         Attachments: rabbit-1-mergelock.log, rabbit-2-mergelock.log

We're getting failures on acquiring locks during merges. Here is the configuration:
Infinispan: 3 caches: lockCache (replicated, volatile, no eviction), metadataCache (replicated, persisted, no eviction), dataCache (distributed, persisted, eviction).
Node 1: coordinator, IndexWriter open constantly and writing a stream of documents
Node 2: opens a read-only IndexReader on-demand to perform queries (we're moving to use IndexReader.reopen() ).

Occasionally when performing queries on node 2 we get the attached stack traces. We then get corrupt indexes (java.io.IOException: Read past EOF).

We are using the default Distributed Segment Lock Reader, default 16K chunks and no tuning of the merge policies.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the infinispan-issues mailing list