[JBoss JIRA] (ISPN-4801) ConcurrentModificationException on the FileListCacheValue
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-4801:
---------------------------------------
Summary: ConcurrentModificationException on the FileListCacheValue
Key: ISPN-4801
URL: https://issues.jboss.org/browse/ISPN-4801
Project: Infinispan
Issue Type: Bug
Components: Embedded Querying
Affects Versions: 7.0.0.Beta2
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Priority: Critical
Fix For: 7.0.0.CR1
Since ISPN-4692 that made FileListCacheValue DeltaAware, the following is happening when running {{org.infinispan.lucene.profiling.PerformanceCompareStressTest}}:
{code}
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:922)
at java.util.HashMap$KeyIterator.next(HashMap.java:956)
at java.util.AbstractCollection.toArray(AbstractCollection.java:195)
at org.infinispan.lucene.impl.FileListCacheValue.toArray(FileListCacheValue.java:109)
at org.infinispan.lucene.impl.FileListOperations.listFilenames(FileListOperations.java:101)
at org.infinispan.lucene.impl.DirectoryImplementor.list(DirectoryImplementor.java:56)
at org.infinispan.lucene.impl.DirectoryLuceneV4.listAll(DirectoryLuceneV4.java:123)
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:759)
{code}
The problem is that the deltas are not being applied in a thread safe manner
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-4792) RemoteClusterListener still invokes filter/converter
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4792?page=com.atlassian.jira.plugin.... ]
Work on ISPN-4792 started by William Burns.
-------------------------------------------
> RemoteClusterListener still invokes filter/converter
> ----------------------------------------------------
>
> Key: ISPN-4792
> URL: https://issues.jboss.org/browse/ISPN-4792
> Project: Infinispan
> Issue Type: Enhancement
> Components: Listeners
> Affects Versions: 7.0.0.Beta2
> Reporter: William Burns
> Assignee: William Burns
>
> When using a distributed cluster listener it installs a listener on each of the nodes to receive notifications. Cluster listeners only raise post events, but on remote nodes (ones where the listener wasn't originally installed) they invoke the filter and converter even on pre events which is not needed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-4792) RemoteClusterListener still invokes filter/converter
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4792?page=com.atlassian.jira.plugin.... ]
William Burns reassigned ISPN-4792:
-----------------------------------
Assignee: William Burns (was: Dan Berindei)
> RemoteClusterListener still invokes filter/converter
> ----------------------------------------------------
>
> Key: ISPN-4792
> URL: https://issues.jboss.org/browse/ISPN-4792
> Project: Infinispan
> Issue Type: Enhancement
> Components: Listeners
> Affects Versions: 7.0.0.Beta2
> Reporter: William Burns
> Assignee: William Burns
>
> When using a distributed cluster listener it installs a listener on each of the nodes to receive notifications. Cluster listeners only raise post events, but on remote nodes (ones where the listener wasn't originally installed) they invoke the filter and converter even on pre events which is not needed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-4792) RemoteClusterListener still invokes filter/converter
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4792?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-4792:
--------------------------------
Status: Open (was: New)
> RemoteClusterListener still invokes filter/converter
> ----------------------------------------------------
>
> Key: ISPN-4792
> URL: https://issues.jboss.org/browse/ISPN-4792
> Project: Infinispan
> Issue Type: Enhancement
> Components: Listeners
> Affects Versions: 7.0.0.Beta2
> Reporter: William Burns
> Assignee: Dan Berindei
>
> When using a distributed cluster listener it installs a listener on each of the nodes to receive notifications. Cluster listeners only raise post events, but on remote nodes (ones where the listener wasn't originally installed) they invoke the filter and converter even on pre events which is not needed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-2622) Random failure in RpcManagerMBeanTest
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-2622?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-2622:
------------------------------------
Looks like initial problem wasn't fixed: the coordinator is incrementing the RPC counter for the final topology update only after all the members have installed that topology, so it can happen after {{waitForRehashCompletion()}} finished.
> Random failure in RpcManagerMBeanTest
> -------------------------------------
>
> Key: ISPN-2622
> URL: https://issues.jboss.org/browse/ISPN-2622
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.2.0.Beta5
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 5.2.0.CR3
>
> Attachments: testEnableJmxStats-0.log
>
>
> The test records the replication counter in RpcManagerImpl at the start of the test and after a put operation, and asserts that it only changed by 1. Occasionally, the assertion fails:
> {noformat}
> java.lang.AssertionError: expected [1] but found [2]
> at org.testng.Assert.fail(Assert.java:89)
> at org.testng.Assert.failNotEquals(Assert.java:489)
> at org.testng.Assert.assertEquals(Assert.java:118)
> at org.testng.Assert.assertEquals(Assert.java:160)
> at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:126)
> {noformat}
> This happens because replication counter is only incremented *after* a successful RPC. The test starts when the cluster is considered "formed", that is when all the nodes are included in the read CH on every node. But that doesn't mean that the RPCs pushing state have finished - a pushing node may still be waiting for a response and so it might increment its replication counter after the start of the test.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-2622) Random failure in RpcManagerMBeanTest
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-2622?page=com.atlassian.jira.plugin.... ]
Dan Berindei reopened ISPN-2622:
--------------------------------
Assignee: Dan Berindei (was: Galder Zamarreño)
Getting the same failure in CI:
http://ci.infinispan.org/viewLog.html?buildId=12615&buildTypeId=bt8&tab=b...
http://ci.infinispan.org/viewLog.html?buildTypeId=Infinispan_MasterHotspo...
> Random failure in RpcManagerMBeanTest
> -------------------------------------
>
> Key: ISPN-2622
> URL: https://issues.jboss.org/browse/ISPN-2622
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.2.0.Beta5
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 5.2.0.CR3
>
> Attachments: testEnableJmxStats-0.log
>
>
> The test records the replication counter in RpcManagerImpl at the start of the test and after a put operation, and asserts that it only changed by 1. Occasionally, the assertion fails:
> {noformat}
> java.lang.AssertionError: expected [1] but found [2]
> at org.testng.Assert.fail(Assert.java:89)
> at org.testng.Assert.failNotEquals(Assert.java:489)
> at org.testng.Assert.assertEquals(Assert.java:118)
> at org.testng.Assert.assertEquals(Assert.java:160)
> at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:126)
> {noformat}
> This happens because replication counter is only incremented *after* a successful RPC. The test starts when the cluster is considered "formed", that is when all the nodes are included in the read CH on every node. But that doesn't mean that the RPCs pushing state have finished - a pushing node may still be waiting for a response and so it might increment its replication counter after the start of the test.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-4025) Cross-Site State Transfer: failure scenarios
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4025?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4025:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.CR1
Resolution: Done
> Cross-Site State Transfer: failure scenarios
> --------------------------------------------
>
> Key: ISPN-4025
> URL: https://issues.jboss.org/browse/ISPN-4025
> Project: Infinispan
> Issue Type: Sub-task
> Components: Cross-Site Replication
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Fix For: 7.0.0.CR1, 7.0.0.Final
>
>
> Needs to handle the following scenarios (at least):
> * join/leave in the consumer site (i.e. site that receives the the state)
> I think NBST will handle most of join scenario. However, the leave scenario needs to be handle carefully or we can loose some key chunks. (easy solution: resend all the chunk?)
> * join/leave in the producer site (i.e. site that sends the state)
> trick scenario. we have to be sure that all keys are really sent! (naive solution: restart the state transfer)
> * state transfer coordinator dies
> the coordinator node is the one that receives the acks when all members has finished sending the keys. Or we replicate its state or we restart the state transfer...
> * site master dies in consumer site
> No idea which keys was already applied or not. need to resend the chunks...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-4751) Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4751:
-------------------------------
Component/s: Loaders and Stores
> Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4751
> URL: https://issues.jboss.org/browse/ISPN-4751
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Reporter: Lance Ess
> Assignee: William Burns
>
> I'm trying to use hibernate-search to host a Lucene index on Amazon S3 but I'm getting the following exception:
> {code}
> Exception in thread "LuceneIndexesData-CloudCacheStore-0" java.lang.IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
> at org.infinispan.loaders.bucket.Bucket.setBucketId(Bucket.java:84)
> at org.infinispan.loaders.cloud.CloudCacheStore.readFromBlob(CloudCacheStore.java:450)
> at org.infinispan.loaders.cloud.CloudCacheStore.scanBlobForExpiredEntries(CloudCacheStore.java:292)
> at org.infinispan.loaders.cloud.CloudCacheStore.purge(CloudCacheStore.java:284)
> at org.infinispan.loaders.cloud.CloudCacheStore.purgeInternal(CloudCacheStore.java:336)
> at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:111)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
> The documentation for persisting Lucene indexes on Amazon-S3 is a little sparse but I think I'm on the right track. I'm trying to start infinispan embedded within my application so I've specified a path to the infinispan XML as follows in my hibernate.cfg.xml
> {code:xml}
> <property name="hibernate.search.default.directory_provider">infinispan</property>
> <property name="hibernate.search.infinispan.configuration_resourcename">infinispan-amazons3.xml</property>
> <property name="hibernate.search.infinispan.chunk_size">300000000</property>
> {code}
> And my infinispan-amazons3.xml is:
> {code:xml}
> <infinispan>
> <default>
> <loaders>
> <cloudStore xmlns="urn:infinispan:config:cloud:5.3"
> cloudService="aws-s3"
> identity="user"
> password="password"
> bucketPrefix="bucket">
> </cloudStore>
> </loaders>
> </default>
> </infinispan>
> {code}
> I'm using the following versions (maven pom.xml)
> {code}
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-search</artifactId>
> <version>4.4.4.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-search-infinispan</artifactId>
> <version>4.4.4.Final</version>
> </dependency>
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-cachestore-cloud</artifactId>
> <version>5.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jclouds.provider</groupId>
> <artifactId>aws-s3</artifactId>
> <version>1.4.1</version>
> </dependency>
> {code}
> I initially thought this was related to ISPN-1909 but my version is after the fix for that issue (5.1.3.CR1, 5.1.3.FINAL)
> FYI here's my maven dependency tree (grepped for infinispan)
> {code}
> $ mvn dependency:tree | grep infinispan
> [INFO] +- org.hibernate:hibernate-search-infinispan:jar:4.4.4.Final:compile
> [INFO] | \- org.infinispan:infinispan-lucene-directory:jar:5.3.0.Final:compile
> [INFO] +- org.infinispan:infinispan-cachestore-cloud:jar:5.3.0.Final:compile
> [INFO] | \- org.infinispan:infinispan-core:jar:5.3.0.Final:compile
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (ISPN-4751) Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4751:
-------------------------------
Assignee: William Burns (was: Mircea Markus)
> Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-4751
> URL: https://issues.jboss.org/browse/ISPN-4751
> Project: Infinispan
> Issue Type: Bug
> Reporter: Lance Ess
> Assignee: William Burns
>
> I'm trying to use hibernate-search to host a Lucene index on Amazon S3 but I'm getting the following exception:
> {code}
> Exception in thread "LuceneIndexesData-CloudCacheStore-0" java.lang.IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)
> at org.infinispan.loaders.bucket.Bucket.setBucketId(Bucket.java:84)
> at org.infinispan.loaders.cloud.CloudCacheStore.readFromBlob(CloudCacheStore.java:450)
> at org.infinispan.loaders.cloud.CloudCacheStore.scanBlobForExpiredEntries(CloudCacheStore.java:292)
> at org.infinispan.loaders.cloud.CloudCacheStore.purge(CloudCacheStore.java:284)
> at org.infinispan.loaders.cloud.CloudCacheStore.purgeInternal(CloudCacheStore.java:336)
> at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:111)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
> The documentation for persisting Lucene indexes on Amazon-S3 is a little sparse but I think I'm on the right track. I'm trying to start infinispan embedded within my application so I've specified a path to the infinispan XML as follows in my hibernate.cfg.xml
> {code:xml}
> <property name="hibernate.search.default.directory_provider">infinispan</property>
> <property name="hibernate.search.infinispan.configuration_resourcename">infinispan-amazons3.xml</property>
> <property name="hibernate.search.infinispan.chunk_size">300000000</property>
> {code}
> And my infinispan-amazons3.xml is:
> {code:xml}
> <infinispan>
> <default>
> <loaders>
> <cloudStore xmlns="urn:infinispan:config:cloud:5.3"
> cloudService="aws-s3"
> identity="user"
> password="password"
> bucketPrefix="bucket">
> </cloudStore>
> </loaders>
> </default>
> </infinispan>
> {code}
> I'm using the following versions (maven pom.xml)
> {code}
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-search</artifactId>
> <version>4.4.4.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-search-infinispan</artifactId>
> <version>4.4.4.Final</version>
> </dependency>
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-cachestore-cloud</artifactId>
> <version>5.3.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jclouds.provider</groupId>
> <artifactId>aws-s3</artifactId>
> <version>1.4.1</version>
> </dependency>
> {code}
> I initially thought this was related to ISPN-1909 but my version is after the fix for that issue (5.1.3.CR1, 5.1.3.FINAL)
> FYI here's my maven dependency tree (grepped for infinispan)
> {code}
> $ mvn dependency:tree | grep infinispan
> [INFO] +- org.hibernate:hibernate-search-infinispan:jar:4.4.4.Final:compile
> [INFO] | \- org.infinispan:infinispan-lucene-directory:jar:5.3.0.Final:compile
> [INFO] +- org.infinispan:infinispan-cachestore-cloud:jar:5.3.0.Final:compile
> [INFO] | \- org.infinispan:infinispan-core:jar:5.3.0.Final:compile
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years