January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5901) Metrics not registered for local caches

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5901?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5901: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1276000|https://bugzilla.redhat.com/show_bug.cgi?id=1276000] from ASSIGNED to CLOSED > Metrics not registered for local caches > --------------------------------------- > > Key: ISPN-5901 > URL: https://issues.jboss.org/browse/ISPN-5901 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.1.Final, 7.2.5.Final, 8.1.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.1.0.Final, 8.0.2.Final, 7.2.6.Final > > > Common cache metrics are not registered for local caches. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3550?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3550: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta1 8.2.0.Final Resolution: Done > Migrate Cassandra cache store to the 6.0 cachestore API > -------------------------------------------------------- > > Key: ISPN-3550 > URL: https://issues.jboss.org/browse/ISPN-3550 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Jakub Markos > Labels: jdg7 > Fix For: 8.2.0.Beta1, 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6046) Server Rolling Upgrade performance improvement

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6046?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6046: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta1 8.2.0.Final Resolution: Done > Server Rolling Upgrade performance improvement > ---------------------------------------------- > > Key: ISPN-6046 > URL: https://issues.jboss.org/browse/ISPN-6046 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > Currently the rolling upgrade requires copying all keys for all entries in the cluster, and then transfer all those keys to the target cluster, that in turn will iterate and obtain the values. With a sufficient amount of data, the key recording can cause OOME -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6052) Support for entry metadata retrieval in the remote iterator

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6052?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6052: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Support for entry metadata retrieval in the remote iterator > ----------------------------------------------------------- > > Key: ISPN-6052 > URL: https://issues.jboss.org/browse/ISPN-6052 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 8.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Beta1, 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6064) Cannot do Hot Rod rolling upgrade between different server versions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6064?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6064: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Cannot do Hot Rod rolling upgrade between different server versions > ------------------------------------------------------------------- > > Key: ISPN-6064 > URL: https://issues.jboss.org/browse/ISPN-6064 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > The server configuration schema is missing the attribute "protocol-version" that allows the Hot Rod data migrator to connect to ealier infinispan versions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6065) HotRodSourceMigrator#recordKnownGlobalKeyset records all keys N times

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6065?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6065: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > HotRodSourceMigrator#recordKnownGlobalKeyset records all keys N times > --------------------------------------------------------------------- > > Key: ISPN-6065 > URL: https://issues.jboss.org/browse/ISPN-6065 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > The task currently uses a Dist. Executor to collect the keys on all nodes, and obtains redundant values -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6053) SegmentKeyTracker not releasing keys for completed segments in the Remote Iterator

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6053?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6053: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > SegmentKeyTracker not releasing keys for completed segments in the Remote Iterator > ---------------------------------------------------------------------------------- > > Key: ISPN-6053 > URL: https://issues.jboss.org/browse/ISPN-6053 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.0.Beta1, 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6089) Distributed Stream doesn't operate in parllel locally

by William Burns (JIRA)

William Burns created ISPN-6089: ----------------------------------- Summary: Distributed Stream doesn't operate in parllel locally Key: ISPN-6089 URL: https://issues.jboss.org/browse/ISPN-6089 Project: Infinispan Issue Type: Bug Components: Distributed Execution and Map/Reduce Affects Versions: 8.0.2.Final, 8.1.0.Final Reporter: William Burns Fix For: 8.2.0.Final, 8.0.3.Final, 8.1.1.Final The distributed stream returns a sequential stream when parallelStream is invoked. We also have to make sure that when parallel is invoked on the stream that this enables parallel streams as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6075) Created cache is immediately available

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6075?page=com.atlassian.jira.plugin.... ] Martin Gencur edited comment on ISPN-6075 at 1/22/16 6:00 AM: -------------------------------------------------------------- My point 3) says that the cache is immediately attached to the remote end-point when it is created. There is no "ignored-caches" element on the endpoint when I create a cache. This is wrong. Right now I need to create the cache AND click disable to have the cache detached. Also, what is the point of showing "Available" when the cache is not attached to a remote endpoint and is de-facto unavailable? Who can use the cache in this state? This is confusing. was (Author: mgencur): My point 3) says that the cache is immediately attached to the remote end-point when it is created. There is no "ignored-caches" element on the endpoint when I create a cache. This is wrong. Right now I need to create the cache AND click disable to have the cache detached. Also, what is the point of showing "Available" when the cache is not attached to a remote endpoint and is de-facto unavailable? Who can use the case in this state? This is confusing. > Created cache is immediately available > -------------------------------------- > > Key: ISPN-6075 > URL: https://issues.jboss.org/browse/ISPN-6075 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > > Steps to reproduce: > 1) Add new cache > 2) Go to the cache detail page > Issues: > 1) The label in top-left corner says "Available" while it should be either Unavailable or Disabled at this point (probably it is because this page still shows the satus of the currentCluster and not the cache itself) > 2) The actions on the right side include both "Disable" and "Enable" and both of them are clickable. Only "Enable" option should be available at this point. > 3) I'm able to create a RemoteCache and put/get entries - no exception thrown -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6075) Created cache is immediately available

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6075?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-6075: ------------------------------------- My point 3) says that the cache is immediately attached to the remote end-point when it is created. There is no "ignored-caches" element on the endpoint when I create a cache. This is wrong. Right now I need to create the cache AND click disable to have the cache detached. Also, what is the point of showing "Available" when the cache is not attached to a remote endpoint and is de-facto unavailable? Who can use the case in this state? This is confusing. > Created cache is immediately available > -------------------------------------- > > Key: ISPN-6075 > URL: https://issues.jboss.org/browse/ISPN-6075 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > > Steps to reproduce: > 1) Add new cache > 2) Go to the cache detail page > Issues: > 1) The label in top-left corner says "Available" while it should be either Unavailable or Disabled at this point (probably it is because this page still shows the satus of the currentCluster and not the cache itself) > 2) The actions on the right side include both "Disable" and "Enable" and both of them are clickable. Only "Enable" option should be available at this point. > 3) I'm able to create a RemoteCache and put/get entries - no exception thrown -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016