March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7544) Administration console - server cards do not indicate correct status in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7544?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7544: -------------------------------------- Status: Open (was: New) > Administration console - server cards do not indicate correct status in some cases > ---------------------------------------------------------------------------------- > > Key: ISPN-7544 > URL: https://issues.jboss.org/browse/ISPN-7544 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > > Server cards (clusters tab -> cluster) don't indicate that the server is in reload-required, restart required state. - they show green check icon in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7544) Administration console - server cards do not indicate correct status in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7544?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7544: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/196 > Administration console - server cards do not indicate correct status in some cases > ---------------------------------------------------------------------------------- > > Key: ISPN-7544 > URL: https://issues.jboss.org/browse/ISPN-7544 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > > Server cards (clusters tab -> cluster) don't indicate that the server is in reload-required, restart required state. - they show green check icon in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7543) Integration tests should try to kill the server before trying to start it

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7543?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7543: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Integration tests should try to kill the server before trying to start it > ------------------------------------------------------------------------- > > Key: ISPN-7543 > URL: https://issues.jboss.org/browse/ISPN-7543 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.0.0.Final > > > Some integration tests use an Ant file to start one or more external servers and then kill them. Sometimes the kill step doesn't run, e.g. in this example the JVM died with an internal error: > http://ci.infinispan.org/viewLog.html?buildId=50891&buildTypeId=bt9&tab=b... > The server then stayed up and caused lots of failures in the test suite runs that followed, apparently without the kill step running in any of those runs. We should add a kill step before trying to start the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7549) Cluster resize helper API

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-7549: --------------------------------------- Summary: Cluster resize helper API Key: ISPN-7549 URL: https://issues.jboss.org/browse/ISPN-7549 Project: Infinispan Issue Type: Enhancement Components: Cloud Integrations, Core Reporter: Gustavo Fernandes Given a topology we should be able to calculate a subset of nodes that can be safely removed from the cluster without incurring data loss; those nodes should not include both a primary owner and a replica. This API can be used as an aid for cloud environments when doing scale down operation, and also for non-cloud environments in order to kill the right nodes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7539) Do not configure data container key/value equivalence in tests

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7539?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7539: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Do not configure data container key/value equivalence in tests > -------------------------------------------------------------- > > Key: ISPN-7539 > URL: https://issues.jboss.org/browse/ISPN-7539 > Project: Infinispan > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final > > > This is deprecated and a no-op anyway. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7548) SimpleCacheImpl streams iterate through the data container twice

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7548?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7548: ------------------------------- Status: Open (was: New) > SimpleCacheImpl streams iterate through the data container twice > ---------------------------------------------------------------- > > Key: ISPN-7548 > URL: https://issues.jboss.org/browse/ISPN-7548 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final > > > {{SimpleCacheImpl.getStreamSupplier()}} uses {{DataContainer.size()}} to estimate the size of the stream, and that method iterates through the data container in order to exclude expired entries. It should use {{DataContainer.sizeIncludingExpired()}} instead, which doesn't iterate through the data container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7548) SimpleCacheImpl streams iterate through the data container twice

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7548?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7548: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4927 > SimpleCacheImpl streams iterate through the data container twice > ---------------------------------------------------------------- > > Key: ISPN-7548 > URL: https://issues.jboss.org/browse/ISPN-7548 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final > > > {{SimpleCacheImpl.getStreamSupplier()}} uses {{DataContainer.size()}} to estimate the size of the stream, and that method iterates through the data container in order to exclude expired entries. It should use {{DataContainer.sizeIncludingExpired()}} instead, which doesn't iterate through the data container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7548) SimpleCacheImpl streams iterate through the data container twice

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7548?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7548: ------------------------------------ {{SimpleCacheImpl.clear()}} also uses {{DataContainer.size()}} when it should be using {{sizeIncludingExpired()}}. > SimpleCacheImpl streams iterate through the data container twice > ---------------------------------------------------------------- > > Key: ISPN-7548 > URL: https://issues.jboss.org/browse/ISPN-7548 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final > > > {{SimpleCacheImpl.getStreamSupplier()}} uses {{DataContainer.size()}} to estimate the size of the stream, and that method iterates through the data container in order to exclude expired entries. It should use {{DataContainer.sizeIncludingExpired()}} instead, which doesn't iterate through the data container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7548) SimpleCacheImpl streams iterate through the data container twice

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7548: ---------------------------------- Summary: SimpleCacheImpl streams iterate through the data container twice Key: ISPN-7548 URL: https://issues.jboss.org/browse/ISPN-7548 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.0.0.CR2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Final {{SimpleCacheImpl.getStreamSupplier()}} uses {{DataContainer.size()}} to estimate the size of the stream, and that method iterates through the data container in order to exclude expired entries. It should use {{DataContainer.sizeIncludingExpired()}} instead, which doesn't iterate through the data container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7540) Calling getCache(String, String) - template overrides cache definition

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7540?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7540: -------------------------------- Status: Open (was: New) > Calling getCache(String, String) - template overrides cache definition > ---------------------------------------------------------------------- > > Key: ISPN-7540 > URL: https://issues.jboss.org/browse/ISPN-7540 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 9.0.0.CR2 > Reporter: William Burns > Assignee: William Burns > > Calling getCache(String, String) on CacheManager will apply the template irrespective if the configuration is already defined. This can cause an issue where the cache doesn't have the desired configuration. We need to do something to either stop this or behave better. > Discussed at http://lists.jboss.org/pipermail/infinispan-dev/2017-February/017245.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017