January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5826) Caches should be stopped in the right order in tests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5826?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5826: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1298379|https://bugzilla.redhat.com/show_bug.cgi?id=1298379] from ON_QA to VERIFIED > Caches should be stopped in the right order in tests > ---------------------------------------------------- > > Key: ISPN-5826 > URL: https://issues.jboss.org/browse/ISPN-5826 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Core, Test Suite - Query > Affects Versions: 8.1.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.1.0.CR1 > > > ISPN-4561 introduced a cache dependency mechanism at the cache manager level, to allow caches to be stopped in a specific order. The test-fw does not use the cache manager to stop caches to avoid rehash and thus stops caches individually, causing lots of exceptions in the query suite. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4851) Make SyncConsistentHashFactory the default CH factory

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4851?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4851: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Make SyncConsistentHashFactory the default CH factory > ----------------------------------------------------- > > Key: ISPN-4851 > URL: https://issues.jboss.org/browse/ISPN-4851 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Affects Versions: 7.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > With ISPN-4682 fixed, SyncConsistentHashFactory should be good enough to be the default. It still allows for more variation in the number of owned segments per node (+/-10% owned segments and +/-20% for primary-owned segments), but that should be acceptable for most purposes. > The major advantage of SCHF is that it depends only on the cache members and not on the order they joined. Users expect a key to map to the same node in all caches (as long as the caches have the same members). > One downside of SCHF, especially for testing, is that the segment ownership differs between test runs (being based on the random address assigned to each node). However, most tests that depend on key ownership should use {{ControlledConsistentHashFactory}} anyway. > We also need to verify that the number of segments moved by SCHF is comparable to the number of segments moved by DefaultConsistentHashFactory (ISPN-3729). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6055) Performance regression in replicated reads after ISPN-5465 and ISPN-5878

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6055?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6055: ---------------------------------- Fix Version/s: 8.2.0.Beta1 8.2.0.Final > Performance regression in replicated reads after ISPN-5465 and ISPN-5878 > ------------------------------------------------------------------------ > > Key: ISPN-6055 > URL: https://issues.jboss.org/browse/ISPN-6055 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Jakub Markos > Assignee: Dan Berindei > Fix For: 8.2.0.Beta1, 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6083) Continuous query and client listeners with DSL filters should reject aggegation queries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6083?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6083: -------------------------------- Description: Aggregation is currently ignored if present. We should report an error instead. At least until ISPN-6060 is implemented. (was: Aggregation is currently ignored if present. We should report an error instead. ) > Continuous query and client listeners with DSL filters should reject aggegation queries > --------------------------------------------------------------------------------------- > > Key: ISPN-6083 > URL: https://issues.jboss.org/browse/ISPN-6083 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 8.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > Aggregation is currently ignored if present. We should report an error instead. At least until ISPN-6060 is implemented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6083) Continuous query and client listeners with DSL filters should reject aggegation queries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6083?page=com.atlassian.jira.plugin.... ] Work on ISPN-6083 started by Adrian Nistor. ------------------------------------------- > Continuous query and client listeners with DSL filters should reject aggegation queries > --------------------------------------------------------------------------------------- > > Key: ISPN-6083 > URL: https://issues.jboss.org/browse/ISPN-6083 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 8.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > Aggregation is currently ignored if present. We should report an error instead. At least until ISPN-6060 is implemented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6083) Continuous query and client listeners with DSL filters should reject aggegation queries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6083?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6083: -------------------------------- Description: Aggregation is currently ignored if present. We should report an error instead. > Continuous query and client listeners with DSL filters should reject aggegation queries > --------------------------------------------------------------------------------------- > > Key: ISPN-6083 > URL: https://issues.jboss.org/browse/ISPN-6083 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 8.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > Aggregation is currently ignored if present. We should report an error instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6083) Continuous query and client listeners with DSL filters should reject aggegation queries

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6083: ----------------------------------- Summary: Continuous query and client listeners with DSL filters should reject aggegation queries Key: ISPN-6083 URL: https://issues.jboss.org/browse/ISPN-6083 Project: Infinispan Issue Type: Bug Components: Embedded Querying, Remote Querying Affects Versions: 8.1.0.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.2.0.Alpha1, 8.1.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6083) Continuous query and client listeners with DSL filters should reject aggegation queries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6083?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6083: -------------------------------- Status: Open (was: New) > Continuous query and client listeners with DSL filters should reject aggegation queries > --------------------------------------------------------------------------------------- > > Key: ISPN-6083 > URL: https://issues.jboss.org/browse/ISPN-6083 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 8.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6077) AddCache dialog only offers cache templates from "clustered" cache container

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6077?page=com.atlassian.jira.plugin.... ] Martin Gencur reassigned ISPN-6077: ----------------------------------- Assignee: Vladimir Blagojevic > AddCache dialog only offers cache templates from "clustered" cache container > ---------------------------------------------------------------------------- > > Key: ISPN-6077 > URL: https://issues.jboss.org/browse/ISPN-6077 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Assignee: Vladimir Blagojevic > > When adding a new cache, the "Base configuration" element only shows options from a cache container named "clustered". If there are different cache containers in the configuration, the select element does not show anything. > The problem is getConfigurationTemplates function in infinispan-management-console/src/main/webapp/components/api/cache-creation-controller.service.js which should take into account different cache container names. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6081) Creating new cache with name that already exists leads to no response in the UI

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6081?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-6081: -------------------------------- Status: Open (was: New) > Creating new cache with name that already exists leads to no response in the UI > ------------------------------------------------------------------------------- > > Key: ISPN-6081 > URL: https://issues.jboss.org/browse/ISPN-6081 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > Priority: Minor > > Steps to reproduce: > Cache container detail page -> Add Cache -> fill in cache name and base configuration -> click Next -> click Create -> click Create on the following screen again > Result: There's an error in the server log but the console does not show any warning. The modal dialog stays open and users don't not know what happened unless they look at server logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

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