March 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, I finally got down to testing migrated Cloud cache store with AWS S3 and found some minor issues (tracked in ISPN-5288) - these should be fixed in [PR #4|https://github.com/infinispan/infinispan-cachestore-cloud/pull/4] and I was able to use Cloud cache store with S3 successfully. However, keeping this issue open until I reproduce exactly this issue and verify that it's fixed (and PR #4 is merged). > 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: Vojtech Juranek > > 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

1
0
0 / 0

[JBoss JIRA] (ISPN-5288) Options for configuring various providers in cloud cache store

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-5288?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-5288: ---------------------------------- Status: Open (was: New) > Options for configuring various providers in cloud cache store > -------------------------------------------------------------- > > Key: ISPN-5288 > URL: https://issues.jboss.org/browse/ISPN-5288 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Make sure that Cloud cache provider can work with various blob stores. > * AWS S3 doesn't allow underscores in bucket names (currently bucket name is create as {{$containername_cachename}}) > * Some providers need to configure API endpoint (e.g. Swift) > * Some providers need to configure additional properties (overriders) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5288) Options for configuring various providers in cloud cache store

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-5288?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-5288: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-cachestore-cloud/pull/4 > Options for configuring various providers in cloud cache store > -------------------------------------------------------------- > > Key: ISPN-5288 > URL: https://issues.jboss.org/browse/ISPN-5288 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Make sure that Cloud cache provider can work with various blob stores. > * AWS S3 doesn't allow underscores in bucket names (currently bucket name is create as {{$containername_cachename}}) > * Some providers need to configure API endpoint (e.g. Swift) > * Some providers need to configure additional properties (overriders) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5288) Options for configuring various providers in cloud cache store

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-5288: ------------------------------------- Summary: Options for configuring various providers in cloud cache store Key: ISPN-5288 URL: https://issues.jboss.org/browse/ISPN-5288 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Reporter: Vojtech Juranek Assignee: Vojtech Juranek Make sure that Cloud cache provider can work with various blob stores. * AWS S3 doesn't allow underscores in bucket names (currently bucket name is create as {{$containername_cachename}}) * Some providers need to configure API endpoint (e.g. Swift) * Some providers need to configure additional properties (overriders) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5287) Inconsistent logging for starting and finished rebalance

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5287?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5287: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1192324 > Inconsistent logging for starting and finished rebalance > -------------------------------------------------------- > > Key: ISPN-5287 > URL: https://issues.jboss.org/browse/ISPN-5287 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.1.1.Final > Reporter: Dan Berindei > > The node-level rebalance completed events are logged at INFO level, but the cluster-wide rebalance completed event is logged only at DEBUG level, which is not visible by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5287) Inconsistent logging for starting and finished rebalance

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5287?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5287: ------------------------------- Affects Version/s: 7.1.1.Final > Inconsistent logging for starting and finished rebalance > -------------------------------------------------------- > > Key: ISPN-5287 > URL: https://issues.jboss.org/browse/ISPN-5287 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Dan Berindei > > The node-level rebalance completed events are logged at INFO level, but the cluster-wide rebalance completed event is logged only at DEBUG level, which is not visible by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5287) Inconsistent logging for starting and finished rebalance

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5287?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5287: ------------------------------- Component/s: Core State Transfer > Inconsistent logging for starting and finished rebalance > -------------------------------------------------------- > > Key: ISPN-5287 > URL: https://issues.jboss.org/browse/ISPN-5287 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.1.1.Final > Reporter: Dan Berindei > > The node-level rebalance completed events are logged at INFO level, but the cluster-wide rebalance completed event is logged only at DEBUG level, which is not visible by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5287) Inconsistent logging for starting and finished rebalance

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5287: ---------------------------------- Summary: Inconsistent logging for starting and finished rebalance Key: ISPN-5287 URL: https://issues.jboss.org/browse/ISPN-5287 Project: Infinispan Issue Type: Bug Reporter: Dan Berindei The node-level rebalance completed events are logged at INFO level, but the cluster-wide rebalance completed event is logged only at DEBUG level, which is not visible by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4810) Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4810?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4810: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1196258|https://bugzilla.redhat.com/show_bug.cgi?id=1196258] from ASSIGNED to POST > Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-4810 > URL: https://issues.jboss.org/browse/ISPN-4810 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Environment: Windows 7 x64 (NTFS) > Oracle JDK1.7.0_40 > Apache Maven 3.0.5 > Reporter: Horia Chiorean > Assignee: William Burns > Labels: modeshape > Attachments: ispn_concurrent.zip > > > Using Infinispan 6.0.2 and a local, transactional cache backed by a <singleFile> store, with eviction enabled and a small {{max-entries}} setting, we have the following scenario: > * the main thread (i.e. the "writer") starts a transaction, adds a batch of strings into the cache and also appends the same strings into a List cache entry and then commits the transaction > * after the above has finished (i.e. after tx.commit) it fires a number of reader threads where each reader thread > ** checks that the string entries were added into the cache and > ** checks that the entries were correctly appended to the List entry > * the above steps are repeated a number of times > On any given run, based on timing, we're seeing that at some point (after some time) some of the reader threads will not see the latest version of the List entry (i.e. will not see the latest elements that were added into the list) but rather an old, stale List (sort of a "lost update" scenario). > If we either: > * disable eviction or > * set the {{max-entries}} to a large enough value (which I suspect has the same effect - not evicting anything) the problem doesn't show up. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5283) Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5283?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5283: ---------------------------------- Priority: Major (was: Blocker) > Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-5283 > URL: https://issues.jboss.org/browse/ISPN-5283 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.2.Final, 7.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > > If a Hot Rod client is connected to two (or more) servers and these servers are stopped the client will not continue to work until this last server is back online. > But even if the client is able to continue, the client will not receive updated cluster topology. > Therefor there is no loadbalacing and failover after this point until the client is restarted. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015