[JBoss JIRA] (ISPN-5401) Align server and embedded exposed management properties
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-5401:
--------------------------------------
Summary: Align server and embedded exposed management properties
Key: ISPN-5401
URL: https://issues.jboss.org/browse/ISPN-5401
Project: Infinispan
Issue Type: Enhancement
Components: JMX, reporting and management
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 7.2.0.Final
Server exposes more attributes than embedded, causing some confusion amongst our users, e.g. isCoordinator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (ISPN-2981) Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-2981?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-2981:
---------------------------------------
[~chp-anujs] that's an interesting approach, but wasn't it simpler to upgrade to the much improved later version of Infinispan? I hope you noticed that this issue is marked as resolved since version 7.0
> Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode
> -------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2981
> URL: https://issues.jboss.org/browse/ISPN-2981
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 5.2.4.Final
> Environment: Hibernate Search 4.1.1, Hibernate Core 4.1.4, Lucene 3.5.0, Spring Framework 3.1.1
> Reporter: Christopher Wong
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.Beta2, 7.0.0.Final
>
> Attachments: infinispan.cfg.xml, luceneindexerrors.txt
>
>
> I have been trying to use Infinispan as a Lucene directory provider under Hibernate Search. A single node writes to the index via JMS. A configuration that uses Infinispan in distributed mode seems to work under development, but under load results in an exception that looks like the following.
> Caused by: java.io.IOException: No sub-file with id .fnm found (fileName=_3.cfs files: [.fdt, .fdx])
> at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:156)
> at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:145)
> at org.apache.lucene.index.FieldInfos.<init>(FieldInfos.java:74)
> at org.apache.lucene.index.SegmentCoreReaders.<init>(SegmentCoreReaders.java:73)
> at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:115)
> at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:93)
> at org.apache.lucene.index.DirectoryReader.<init>(DirectoryReader.java:235)
> at org.apache.lucene.index.ReadOnlyDirectoryReader.<init>(ReadOnlyDirectoryReader.java:34)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:506)
> at org.apache.lucene.index.DirectoryReader.access$000(DirectoryReader.java:45)
> at org.apache.lucene.index.DirectoryReader$2.doBody(DirectoryReader.java:498)
> at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:754)
> at org.apache.lucene.index.DirectoryReader.doOpenNoWriter(DirectoryReader.java:493)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:450)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:391)
> at org.apache.lucene.index.IndexReader.openIfChanged(IndexReader.java:497)
> at org.apache.lucene.index.IndexReader.reopen(IndexReader.java:681)
> at org.hibernate.search.indexes.impl.SharingBufferReaderProvider$PerDirectoryLatestReader.refreshAndGet(SharingBufferReaderProvider.java:227)
> ... 117 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (ISPN-5103) Inefficient index updates cause high cost merges and increase overall latency
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5103?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5103:
-----------------------------------------------
Richa <rmarwaha(a)redhat.com> changed the Status of [bug 1175382|https://bugzilla.redhat.com/show_bug.cgi?id=1175382] from ASSIGNED to CLOSED
> Inefficient index updates cause high cost merges and increase overall latency
> -----------------------------------------------------------------------------
>
> Key: ISPN-5103
> URL: https://issues.jboss.org/browse/ISPN-5103
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying
> Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 7.1.0.Beta1
>
>
> Currently every change to the index is done Lucene-wise combining two operations:
> * Delete by query, using a boolean query on the id plus the entity class
> * Add
>
> Under high load, specially during merges those numerous deletes provoke very long delays causing high latency.
> We should instead use a simple Lucene Update to add/change documents, since internally it translates to a Delete by term plus an Add operation, and delete by terms are extremely efficient in Lucene.
> Some local tests showed average latency of updating the index using this strategy to drop 4 times, both for the SYNC and ASYNC backends
> With relation to sharing the index between entities, which was the original motivation of the Delete by query plus add strategy, we have two scenarios:
> * Same cache with multiple entity types: that's a non-issue, since obviously there's no id collision in this case
> * Different caches with the same index: this scenario happens when different caches shares the same index, for ex:
> {code}
> @Indexed(indexName=common)
> public class Country { ... }
> @Indexed(indexName=common)
> public class Currency { ... }
> cm.getCache("currencies").put(1, new Currency(...))
> cm.getCache("countries").put(1, new Country(...))
> {code}
> This would require a delete by query in order to persist both a Country and a Currency with id=1.
> It would also require setting "default.exclusive_index_use", "false", with the associated cost of having to reopen the IndexWriter on every operation.
> Given the performance gain of doing a simple Update is considerable, we should make the corner case supported by extra configuration or alternatively, generate a unique @ProvidedId, including the entity class or the cache name that work for all cases described above.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (ISPN-2981) Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode
by Anuj Shah (JIRA)
[ https://issues.jboss.org/browse/ISPN-2981?page=com.atlassian.jira.plugin.... ]
Anuj Shah edited comment on ISPN-2981 at 4/22/15 5:26 AM:
----------------------------------------------------------
The description here related to distributed caches, however we've seen the same problem occur with the same stack trace with replicated caches on a single node cluster and Infinispan 5.2.6
We've worked around the problem be preventing concurrent merges and addressing the following comment in [LUCENE-5541|https://issues.apache.org/jira/browse/LUCENE-5541?focusedComm...]
bq. A Merge is writing concurrently to a thread using an IndexWriter for doing new writes
was (Author: chp-anujs):
The description here related to distributed caches, however we've seen the same problem occur with the same stack trace with replicated caches on a single node cluster.
We've worked around the problem be preventing concurrent merges and addressing the following comment in [LUCENE-5541|https://issues.apache.org/jira/browse/LUCENE-5541?focusedComm...]
bq. A Merge is writing concurrently to a thread using an IndexWriter for doing new writes
> Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode
> -------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2981
> URL: https://issues.jboss.org/browse/ISPN-2981
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 5.2.4.Final
> Environment: Hibernate Search 4.1.1, Hibernate Core 4.1.4, Lucene 3.5.0, Spring Framework 3.1.1
> Reporter: Christopher Wong
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.Beta2, 7.0.0.Final
>
> Attachments: infinispan.cfg.xml, luceneindexerrors.txt
>
>
> I have been trying to use Infinispan as a Lucene directory provider under Hibernate Search. A single node writes to the index via JMS. A configuration that uses Infinispan in distributed mode seems to work under development, but under load results in an exception that looks like the following.
> Caused by: java.io.IOException: No sub-file with id .fnm found (fileName=_3.cfs files: [.fdt, .fdx])
> at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:156)
> at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:145)
> at org.apache.lucene.index.FieldInfos.<init>(FieldInfos.java:74)
> at org.apache.lucene.index.SegmentCoreReaders.<init>(SegmentCoreReaders.java:73)
> at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:115)
> at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:93)
> at org.apache.lucene.index.DirectoryReader.<init>(DirectoryReader.java:235)
> at org.apache.lucene.index.ReadOnlyDirectoryReader.<init>(ReadOnlyDirectoryReader.java:34)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:506)
> at org.apache.lucene.index.DirectoryReader.access$000(DirectoryReader.java:45)
> at org.apache.lucene.index.DirectoryReader$2.doBody(DirectoryReader.java:498)
> at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:754)
> at org.apache.lucene.index.DirectoryReader.doOpenNoWriter(DirectoryReader.java:493)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:450)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:391)
> at org.apache.lucene.index.IndexReader.openIfChanged(IndexReader.java:497)
> at org.apache.lucene.index.IndexReader.reopen(IndexReader.java:681)
> at org.hibernate.search.indexes.impl.SharingBufferReaderProvider$PerDirectoryLatestReader.refreshAndGet(SharingBufferReaderProvider.java:227)
> ... 117 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (ISPN-2981) Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode
by Anuj Shah (JIRA)
[ https://issues.jboss.org/browse/ISPN-2981?page=com.atlassian.jira.plugin.... ]
Anuj Shah commented on ISPN-2981:
---------------------------------
The description here related to distributed caches, however we've seen the same problem occur with the same stack trace with replicated caches on a single node cluster.
We've worked around the problem be preventing concurrent merges and addressing the following comment in [LUCENE-5541|https://issues.apache.org/jira/browse/LUCENE-5541?focusedComm...]
bq. A Merge is writing concurrently to a thread using an IndexWriter for doing new writes
> Infinispan as Lucene directory provider has "No sub-file with id .fnm found" errors in distributed mode
> -------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2981
> URL: https://issues.jboss.org/browse/ISPN-2981
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 5.2.4.Final
> Environment: Hibernate Search 4.1.1, Hibernate Core 4.1.4, Lucene 3.5.0, Spring Framework 3.1.1
> Reporter: Christopher Wong
> Assignee: Gustavo Fernandes
> Fix For: 7.0.0.Beta2, 7.0.0.Final
>
> Attachments: infinispan.cfg.xml, luceneindexerrors.txt
>
>
> I have been trying to use Infinispan as a Lucene directory provider under Hibernate Search. A single node writes to the index via JMS. A configuration that uses Infinispan in distributed mode seems to work under development, but under load results in an exception that looks like the following.
> Caused by: java.io.IOException: No sub-file with id .fnm found (fileName=_3.cfs files: [.fdt, .fdx])
> at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:156)
> at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:145)
> at org.apache.lucene.index.FieldInfos.<init>(FieldInfos.java:74)
> at org.apache.lucene.index.SegmentCoreReaders.<init>(SegmentCoreReaders.java:73)
> at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:115)
> at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:93)
> at org.apache.lucene.index.DirectoryReader.<init>(DirectoryReader.java:235)
> at org.apache.lucene.index.ReadOnlyDirectoryReader.<init>(ReadOnlyDirectoryReader.java:34)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:506)
> at org.apache.lucene.index.DirectoryReader.access$000(DirectoryReader.java:45)
> at org.apache.lucene.index.DirectoryReader$2.doBody(DirectoryReader.java:498)
> at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:754)
> at org.apache.lucene.index.DirectoryReader.doOpenNoWriter(DirectoryReader.java:493)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:450)
> at org.apache.lucene.index.DirectoryReader.doOpenIfChanged(DirectoryReader.java:391)
> at org.apache.lucene.index.IndexReader.openIfChanged(IndexReader.java:497)
> at org.apache.lucene.index.IndexReader.reopen(IndexReader.java:681)
> at org.hibernate.search.indexes.impl.SharingBufferReaderProvider$PerDirectoryLatestReader.refreshAndGet(SharingBufferReaderProvider.java:227)
> ... 117 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months