April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5343) Make eviction max-entries parameter configurable at runtime

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5343?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5343: ---------------------------------- Fix Version/s: 8.0.0.Final > Make eviction max-entries parameter configurable at runtime > ----------------------------------------------------------- > > Key: ISPN-5343 > URL: https://issues.jboss.org/browse/ISPN-5343 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 7.2.0.Beta2 > Environment: Infinispan 7/ JDG > Reporter: Duncan Doyle > Assignee: William Burns > Fix For: 8.0.0.Final > > > I've got a use-case where I would like to be able to dynamically (at runtime) configure the max-entries parameter of my eviction configuration. This would allow to, for example, decrease the max-entries dynamically when my system starts running oom. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5343) Make eviction max-entries parameter configurable at runtime

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5343?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-5343: ------------------------------------- Assignee: William Burns > Make eviction max-entries parameter configurable at runtime > ----------------------------------------------------------- > > Key: ISPN-5343 > URL: https://issues.jboss.org/browse/ISPN-5343 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 7.2.0.Beta2 > Environment: Infinispan 7/ JDG > Reporter: Duncan Doyle > Assignee: William Burns > > I've got a use-case where I would like to be able to dynamically (at runtime) configure the max-entries parameter of my eviction configuration. This would allow to, for example, decrease the max-entries dynamically when my system starts running oom. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5343) Make eviction max-entries parameter configurable at runtime

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5343?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5343: ---------------------------------- Status: Open (was: New) > Make eviction max-entries parameter configurable at runtime > ----------------------------------------------------------- > > Key: ISPN-5343 > URL: https://issues.jboss.org/browse/ISPN-5343 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 7.2.0.Beta2 > Environment: Infinispan 7/ JDG > Reporter: Duncan Doyle > Assignee: William Burns > > I've got a use-case where I would like to be able to dynamically (at runtime) configure the max-entries parameter of my eviction configuration. This would allow to, for example, decrease the max-entries dynamically when my system starts running oom. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5375) Some CLI commands (evict, rm) are not codec-aware

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5375?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5375: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3378 > Some CLI commands (evict, rm) are not codec-aware > ------------------------------------------------- > > Key: ISPN-5375 > URL: https://issues.jboss.org/browse/ISPN-5375 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 7.2.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.CR1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5375) Some CLI commands (evict, rm) are not codec-aware

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5375?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5375: ---------------------------------- Status: Open (was: New) > Some CLI commands (evict, rm) are not codec-aware > ------------------------------------------------- > > Key: ISPN-5375 > URL: https://issues.jboss.org/browse/ISPN-5375 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 7.2.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.CR1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-4751: --------------------------------------- I see. [~hardy.ferentschik] is working on a completely new Faceting engine; it's going to take a bit longer but please make sure your specific requirements are filed in the Hibernate JIRA so we can take that into account. Feel free to create new issues and link them to https://hibernate.atlassian.net/browse/HSEARCH-809 Regarding testing this specific Infinispan issue, I just verified that the Hibernate Search SPI is unchanged so technically one could use the hibernate-search-infinispan Maven module from version 5.1 with the older versions of hibernate-search-engine and hibernate-search-orm, but you'd also need a Lucene Directory module from Infinispan to support Lucene v3 (new Hibernate Search and Infinispan are using Apache Lucene 4 now). Changing Lucene version is far from simple so I wouldn't suggest that, sorry you'd need to upgrade Search version all-in. Thanks to you for all updates! > 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)

10 years, 12 months

1
0
0 / 0

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

by George Christman (JIRA)

[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ] George Christman commented on ISPN-4751: ---------------------------------------- Thanks Sanne, That is the news I've been dreading, there has been some major api changes in 5.1 breaking the way I handle multiple value facet counts like shown here http://outbottle.com/hibernate-search-multivalue-facet-counts/ I'll make the upgrade to 5.1 so we can get this issue closed out, but I'll probably have some questions in regards to repairing the multiple value facet counts on SO. Thanks for all the hard work. > 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)

10 years, 12 months

1
0
0 / 0

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

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4751?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-4751: --------------------------------------- Hi [~gchristman], to use Infinispan 7.1.1.Final you should use Hibernate Search 5.1.1.Final That older Hibernate Search 4.5.1 is requiring Infinispan 6: unfortunately the integration points are not compatible across major versions of Infinispan. > 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)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5368) Out of order events produced when using the MassIndexer with async backend

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5368?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5368: ------------------------------------ Status: Open (was: New) > Out of order events produced when using the MassIndexer with async backend > -------------------------------------------------------------------------- > > Key: ISPN-5368 > URL: https://issues.jboss.org/browse/ISPN-5368 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > When using async indexing backend on DIST caches with shared index (InfinispanIndexManager), the MassIndexer fails to re-index all the entries, if it is run from a node that is not > the indexing master. > Normally the operation sequence of the MassIndexer in the above configuration, for a two node cluster is: > * Purge the index > * Send index job to node A and to node B > * Flush > Given the backend is async, all index commands are sent to the master RPC-wise asynchronously, and so a reorder can occur and produce like: > * Send index job to node A > * Purge > * Send index job to node B > * Flush > Causing previously re-indexed entries to be wiped -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5368) Out of order events produced when using the MassIndexer with async backend

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5368?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5368: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3377 > Out of order events produced when using the MassIndexer with async backend > -------------------------------------------------------------------------- > > Key: ISPN-5368 > URL: https://issues.jboss.org/browse/ISPN-5368 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > When using async indexing backend on DIST caches with shared index (InfinispanIndexManager), the MassIndexer fails to re-index all the entries, if it is run from a node that is not > the indexing master. > Normally the operation sequence of the MassIndexer in the above configuration, for a two node cluster is: > * Purge the index > * Send index job to node A and to node B > * Flush > Given the backend is async, all index commands are sent to the master RPC-wise asynchronously, and so a reorder can occur and produce like: > * Send index job to node A > * Purge > * Send index job to node B > * Flush > Causing previously re-indexed entries to be wiped -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 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 April 2015