January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4751) Hibernate search, infinispan and Amazon S3 - IllegalArgumentException: bucketId: A96137216.bz2 (expected: integer)

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ] Vojtech Juranek commented on ISPN-4751: --------------------------------------- Hi, [~gchristman] I'm going to work on ISPN-3549, once done, some progress with this issue can be expected as well :-) > 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.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3549) Migrate cloud cache store to the 7.0 cachestore API

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-3549?page=com.atlassian.jira.plugin.... ] Vojtech Juranek commented on ISPN-3549: --------------------------------------- Hi, > So how much work would be necessary to update this implementation to at least Infinispan 6 (in case Infinispan 7 introduced more radical changes)? I'm going to migrate it to ISPN 7 and there are quite a lot of changes need to be done as the API has change a lot. >More important that the version number itself is the fact the Jclouds 1.8.1 has removed support for async operations IMHO we should update to recent JClouds version and implement async operations eventually ourselves > Migrate cloud cache store to the 7.0 cachestore API > ---------------------------------------------------- > > Key: ISPN-3549 > URL: https://issues.jboss.org/browse/ISPN-3549 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Vojtech Juranek > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3549) Migrate cloud cache store to the 6.0 cachestore API

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-3549?page=com.atlassian.jira.plugin.... ] Vojtech Juranek reassigned ISPN-3549: ------------------------------------- Assignee: Vojtech Juranek (was: Tristan Tarrant) > Migrate cloud cache store to the 6.0 cachestore API > ---------------------------------------------------- > > Key: ISPN-3549 > URL: https://issues.jboss.org/browse/ISPN-3549 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Vojtech Juranek > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3549) Migrate cloud cache store to the 7.0 cachestore API

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-3549?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-3549: ---------------------------------- Summary: Migrate cloud cache store to the 7.0 cachestore API (was: Migrate cloud cache store to the 6.0 cachestore API) > Migrate cloud cache store to the 7.0 cachestore API > ---------------------------------------------------- > > Key: ISPN-3549 > URL: https://issues.jboss.org/browse/ISPN-3549 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Vojtech Juranek > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5060) PartitionHandling: remove unavailable mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5060?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5060: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1179926 > PartitionHandling: remove unavailable mode > ------------------------------------------ > > Key: ISPN-5060 > URL: https://issues.jboss.org/browse/ISPN-5060 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.0.2.Final, 7.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.1.0.Final > > > The Unavailable mode name is misleading, because some keys are available, just like in Degraded mode. > The only difference between Degraded and Unavailable is that with Degraded the cluster might recover without manual intervention. The administrator still has to know a lot more details in order to decide whether manual intervention is needed or not. So it would be less confusing if gracefully shutting down {{numOwners}} nodes in quick succession would leave the cache in Degraded mode instead of Unavailable. > Instead of removing the Unavailable mode completely, we could also change it to deny access to all the keys and allow the administrator to use it. E.g. if we had an operation to dump the cache into a shared store and another to load the cache from a shared store, the administrator could force the cache into Unavailable mode while dumping/loading the cache. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5127) LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys random failures

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5127: ---------------------------------- Summary: LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys random failures Key: ISPN-5127 URL: https://issues.jboss.org/browse/ISPN-5127 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 7.0.3.Final, 7.1.0.Alpha1 Reporter: Dan Berindei Priority: Blocker Fix For: 7.1.0.Final Sometimes the filtered retriever doesn't return any entries: {noformat} 15:16:26,328 ERROR (testng-LocalEntryRetrieverWithStoreAsBinaryTest:) [UnitTestTestNGListener] Test testFilterWithStoreAsBinaryPartialKeys(org.infinispan.iteration.LocalEntryRetrieverWithStoreAsBinaryTest) failed.java.util.NoSuchElementException at org.infinispan.iteration.impl.LocalEntryRetriever$Itr.next(LocalEntryRetriever.java:486) at org.infinispan.iteration.impl.LocalEntryRetriever$Itr.next(LocalEntryRetriever.java:428) at org.infinispan.iteration.LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys(LocalEntryRetrieverWithStoreAsBinaryTest.java:93) {noformat} http://ci.infinispan.org/viewLog.html?buildId=14964 The test should also use custom key/value types, as {{String}} keys/values are not marshalled when {{storeAsBinary}} is enabled (see {{MarshalledValue.isTypeExcluded()}}). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5127) LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5127?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5127: ------------------------------- Status: Open (was: New) > LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys random failures > ----------------------------------------------------------------------------------------------- > > Key: ISPN-5127 > URL: https://issues.jboss.org/browse/ISPN-5127 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.Alpha1, 7.0.3.Final > Reporter: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.1.0.Final > > > Sometimes the filtered retriever doesn't return any entries: > {noformat} > 15:16:26,328 ERROR (testng-LocalEntryRetrieverWithStoreAsBinaryTest:) [UnitTestTestNGListener] Test testFilterWithStoreAsBinaryPartialKeys(org.infinispan.iteration.LocalEntryRetrieverWithStoreAsBinaryTest) failed.java.util.NoSuchElementException > at org.infinispan.iteration.impl.LocalEntryRetriever$Itr.next(LocalEntryRetriever.java:486) > at org.infinispan.iteration.impl.LocalEntryRetriever$Itr.next(LocalEntryRetriever.java:428) > at org.infinispan.iteration.LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys(LocalEntryRetrieverWithStoreAsBinaryTest.java:93) > {noformat} > http://ci.infinispan.org/viewLog.html?buildId=14964 > The test should also use custom key/value types, as {{String}} keys/values are not marshalled when {{storeAsBinary}} is enabled (see {{MarshalledValue.isTypeExcluded()}}). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5127) LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5127?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-5127: ---------------------------------- Assignee: William Burns > LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys random failures > ----------------------------------------------------------------------------------------------- > > Key: ISPN-5127 > URL: https://issues.jboss.org/browse/ISPN-5127 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.Alpha1, 7.0.3.Final > Reporter: Dan Berindei > Assignee: William Burns > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.1.0.Final > > > Sometimes the filtered retriever doesn't return any entries: > {noformat} > 15:16:26,328 ERROR (testng-LocalEntryRetrieverWithStoreAsBinaryTest:) [UnitTestTestNGListener] Test testFilterWithStoreAsBinaryPartialKeys(org.infinispan.iteration.LocalEntryRetrieverWithStoreAsBinaryTest) failed.java.util.NoSuchElementException > at org.infinispan.iteration.impl.LocalEntryRetriever$Itr.next(LocalEntryRetriever.java:486) > at org.infinispan.iteration.impl.LocalEntryRetriever$Itr.next(LocalEntryRetriever.java:428) > at org.infinispan.iteration.LocalEntryRetrieverWithStoreAsBinaryTest.testFilterWithStoreAsBinaryPartialKeys(LocalEntryRetrieverWithStoreAsBinaryTest.java:93) > {noformat} > http://ci.infinispan.org/viewLog.html?buildId=14964 > The test should also use custom key/value types, as {{String}} keys/values are not marshalled when {{storeAsBinary}} is enabled (see {{MarshalledValue.isTypeExcluded()}}). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5126) DistributedExecutorService ignores unsuccessful responses

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5126?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5126: ------------------------------- Fix Version/s: 7.1.0.Final > DistributedExecutorService ignores unsuccessful responses > --------------------------------------------------------- > > Key: ISPN-5126 > URL: https://issues.jboss.org/browse/ISPN-5126 > Project: Infinispan > Issue Type: Bug > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 7.1.0.Alpha1, 7.0.3.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Priority: Critical > Labels: testsuite_stability > Fix For: 7.1.0.Final > > > I got a failure in {{DistributedExecutorFailureTest}} (master only) on my machine because the distributed executor ignores {{CacheNotFoundResponse}} responses: > {noformat} > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [CommandAwareRpcDispatcher] Response: CacheNotFoundResponse > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [RpcManagerImpl] Response(s) to DistributedExecuteCommand [cache=null, keys=[], callable=org.infinispan.distexec.DistributedExecutorFailoverTest$SleepingSimpleCallable@23a9b62a] is {NodeB-4305=CacheNotFoundResponse} > 15:18:45,517 ERROR (testng-DistributedExecutorFailoverTest:) [UnitTestTestNGListener] Test testBasicTargetRemoteDistributedCallable(org.infinispan.distexec.DistributedExecutorFailoverTest) failed. > java.lang.AssertionError: expected:<1> but was:<null> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.distexec.DistributedExecutorFailoverTest.testBasicTargetRemoteDistributedCallable(DistributedExecutorFailoverTest.java:74) > {noformat} > {{RemoteDistributedTaskPart.retrieveResult()}} ignores any response that's not a {{SuccessfulResponse}} and returns {{null}}. It should throw an exception instead, so that the failover policy can retry it on another node. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5126) DistributedExecutorService ignores unsuccessful responses

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5126?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-5126: ------------------------------------------- Got it. I'll throw ExecutionException with response details (Response.toString()) > DistributedExecutorService ignores unsuccessful responses > --------------------------------------------------------- > > Key: ISPN-5126 > URL: https://issues.jboss.org/browse/ISPN-5126 > Project: Infinispan > Issue Type: Bug > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 7.1.0.Alpha1, 7.0.3.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Priority: Critical > Labels: testsuite_stability > > I got a failure in {{DistributedExecutorFailureTest}} (master only) on my machine because the distributed executor ignores {{CacheNotFoundResponse}} responses: > {noformat} > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [CommandAwareRpcDispatcher] Response: CacheNotFoundResponse > 15:18:45,516 TRACE (transport-thread-NodeA-p30129-t4:) [RpcManagerImpl] Response(s) to DistributedExecuteCommand [cache=null, keys=[], callable=org.infinispan.distexec.DistributedExecutorFailoverTest$SleepingSimpleCallable@23a9b62a] is {NodeB-4305=CacheNotFoundResponse} > 15:18:45,517 ERROR (testng-DistributedExecutorFailoverTest:) [UnitTestTestNGListener] Test testBasicTargetRemoteDistributedCallable(org.infinispan.distexec.DistributedExecutorFailoverTest) failed. > java.lang.AssertionError: expected:<1> but was:<null> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.distexec.DistributedExecutorFailoverTest.testBasicTargetRemoteDistributedCallable(DistributedExecutorFailoverTest.java:74) > {noformat} > {{RemoteDistributedTaskPart.retrieveResult()}} ignores any response that's not a {{SuccessfulResponse}} and returns {{null}}. It should throw an exception instead, so that the failover policy can retry it on another node. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2015