February 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5232) Entry iterator returns entries created in current TX but does not apply the filter/converter

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5232?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5232: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3274 > Entry iterator returns entries created in current TX but does not apply the filter/converter > -------------------------------------------------------------------------------------------- > > Key: ISPN-5232 > URL: https://issues.jboss.org/browse/ISPN-5232 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.2.0.Beta1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5232) Entry iterator returns entries created in current TX but does not apply the filter/converter

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5232?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5232: -------------------------------- Fix Version/s: 7.2.0.Beta1 > Entry iterator returns entries created in current TX but does not apply the filter/converter > -------------------------------------------------------------------------------------------- > > Key: ISPN-5232 > URL: https://issues.jboss.org/browse/ISPN-5232 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.2.0.Beta1, 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ] Tomas Sykora edited comment on ISPN-5234 at 2/27/15 11:26 AM: -------------------------------------------------------------- review request :P https://github.com/infinispan/infinispan-management-console/pull/5 please, see also frontend, doing changes so we like it even more should be easy now. (still much to do but sending what I have on FRI EOD as I promised) was (Author: tsykora): review request :P https://github.com/infinispan/infinispan-management-console/pull/5 please, see also frontend, doing changes so we like it even more should be easy now. > Implement single cluster view page (P1) > --------------------------------------- > > Key: ISPN-5234 > URL: https://issues.jboss.org/browse/ISPN-5234 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 8.0.0.Final > > > In our admin console current single cluster view page does not contain the following functionality that should be implemented: > * -Zoom in/out- > * Node availability/detail > * Filter by metrics (node view) > * Filter by metrics (cache view) > * Search node (search as you type) > * Search cache (search as you type) > * -Cluster switcher- > * Cluster status view -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-5234: ------------------------------------ review request :P https://github.com/infinispan/infinispan-management-console/pull/5 please, see also frontend, doing changes so we like it even more should be easy now. > Implement single cluster view page (P1) > --------------------------------------- > > Key: ISPN-5234 > URL: https://issues.jboss.org/browse/ISPN-5234 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 8.0.0.Final > > > In our admin console current single cluster view page does not contain the following functionality that should be implemented: > * -Zoom in/out- > * Node availability/detail > * Filter by metrics (node view) > * Filter by metrics (cache view) > * Search node (search as you type) > * Search cache (search as you type) > * -Cluster switcher- > * Cluster status view -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-5234: ------------------------------------ The problem is that the path you would ask for cluster availability is: /profile=clustered/subsystem=infinispan/cache-container=clustered And this path does not provide those information. We need to ask the runtime path /host=master/server=server-one/subsystem=infinispan/cache-container=clustered which provides: cluster-availability=AVAILABLE attribute ;) Working on it. > Implement single cluster view page (P1) > --------------------------------------- > > Key: ISPN-5234 > URL: https://issues.jboss.org/browse/ISPN-5234 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 8.0.0.Final > > > In our admin console current single cluster view page does not contain the following functionality that should be implemented: > * -Zoom in/out- > * Node availability/detail > * Filter by metrics (node view) > * Filter by metrics (cache view) > * Search node (search as you type) > * Search cache (search as you type) > * -Cluster switcher- > * Cluster status view -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5232) Entry iterator returns entries created in current TX but does not apply the filter/converter

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5232?page=com.atlassian.jira.plugin.... ] Work on ISPN-5232 started by William Burns. ------------------------------------------- > Entry iterator returns entries created in current TX but does not apply the filter/converter > -------------------------------------------------------------------------------------------- > > Key: ISPN-5232 > URL: https://issues.jboss.org/browse/ISPN-5232 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3023) Re-implement BoundedConcurrentHashMap using CHMv8 designs

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3023?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3023: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3265 > Re-implement BoundedConcurrentHashMap using CHMv8 designs > --------------------------------------------------------- > > Key: ISPN-3023 > URL: https://issues.jboss.org/browse/ISPN-3023 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Eviction > Affects Versions: 5.2.5.Final > Reporter: Manik Surtani > Assignee: William Burns > Priority: Minor > Labels: performance > Fix For: 7.2.0.Final > > > This is better than the current segment-based approach, in terms of memory footprint as well as performance under high concurrency. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-5234: ------------------------------------------- Isn't this already implemented in cluster-model.services.js, function getAvailability - we need to implement it though? It needs to actually check availability rather than simply returning true. > Implement single cluster view page (P1) > --------------------------------------- > > Key: ISPN-5234 > URL: https://issues.jboss.org/browse/ISPN-5234 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 8.0.0.Final > > > In our admin console current single cluster view page does not contain the following functionality that should be implemented: > * -Zoom in/out- > * Node availability/detail > * Filter by metrics (node view) > * Filter by metrics (cache view) > * Search node (search as you type) > * Search cache (search as you type) > * -Cluster switcher- > * Cluster status view -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[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: --------------------------------------- I'm going to test updated cloud cache store (besides other) with S3 and if everything looks good, the PR will merged and available for use. Once done (general testing with S3), I'll to reproduce specifically this issue and verify that it's fixed by ISPN-3549 (and eventually propose the fix if the issue still remains). > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4033) ConcurrentInterceptorVisibilityTest.testGetVisibility random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4033?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4033: ------------------------------------ The timeout error seems to be caused by very long GC pauses: {noformat} [16:31:20] : [org.infinispan:infinispan-core] 490.847: [GC490.848: [ParNew (promotion failed): 95104K->95104K(95104K), 14.8925940 secs]505.740: [CMS506.524: [CMS-concurrent-sweep: 0.902/15.823 secs] [Times: user=19.15 sys=6.03, real=15.82 secs] [16:31:22] : [org.infinispan:infinispan-core] (concurrent mode failure): 812577K->317912K(838912K), 3.2331000 secs] 869638K->317912K(934016K), [CMS Perm : 48980K->48757K(80104K)], 18.1268550 secs] [Times: user=20.99 sys=5.90, real=18.12 secs] {noformat} The pause seems excessive for just 300MB, so it could have something to do with the OS1 machine the build is running on. Changing the collector to G1 looks promising, with maximum pauses of about 2 seconds, but that's still a little high so I'm trying to see if it can avoid Full GCs completely. > ConcurrentInterceptorVisibilityTest.testGetVisibility random failures > --------------------------------------------------------------------- > > Key: ISPN-4033 > URL: https://issues.jboss.org/browse/ISPN-4033 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Labels: testsuite_stability > Attachments: ConcurrentInterceptorVisibilityTest.log > > > http://ci.infinispan.org/viewLog.html?buildId=5934&tab=buildResultsDiv&bu... > {noformat} > 17:28:43,212 ERROR (testng-ConcurrentInterceptorVisibilityTest:) [UnitTestTestNGListener] Test testGetVisibility(org.infinispan.interceptors.ConcurrentInterceptorVisibilityTest) failed. > java.lang.RuntimeException: java.util.concurrent.TimeoutException > at org.infinispan.interceptors.ConcurrentInterceptorVisibilityTest$1.call(ConcurrentInterceptorVisibilityTest.java:101) > at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1243) > at org.infinispan.interceptors.ConcurrentInterceptorVisibilityTest.updateCache(ConcurrentInterceptorVisibilityTest.java:52) > at org.infinispan.interceptors.ConcurrentInterceptorVisibilityTest.testGetVisibility(ConcurrentInterceptorVisibilityTest.java:39) > Caused by: java.util.concurrent.TimeoutException > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:228) > at java.util.concurrent.FutureTask.get(FutureTask.java:91) > at org.infinispan.interceptors.ConcurrentInterceptorVisibilityTest$1.call(ConcurrentInterceptorVisibilityTest.java:97) > ... 24 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2015