March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6422) ServerEventLoggerTest.testClusteredServerEventLogging fails randomly

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6422: ----------------------------------- Summary: ServerEventLoggerTest.testClusteredServerEventLogging fails randomly Key: ISPN-6422 URL: https://issues.jboss.org/browse/ISPN-6422 Project: Infinispan Issue Type: Bug Components: Server Reporter: Adrian Nistor Assignee: Tristan Tarrant Fix For: 9.0.0.Alpha1 http://ci.infinispan.org/viewLog.html?buildId=37676&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6394) Coalesce server group view and Infinispan/JGroups view

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6394?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6394: ---------------------------------- Priority: Critical (was: Major) > Coalesce server group view and Infinispan/JGroups view > ------------------------------------------------------ > > Key: ISPN-6394 > URL: https://issues.jboss.org/browse/ISPN-6394 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Critical > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > Currently the console is using the server-group knowledge (i.e. which host/servers belong to a specific group). While that is definitely the "ideal" situation, we also need to ensure that it corresponds to the "actual" cluster as known to Infinispan/JGroups. This information should be then used to present the user with appropriate warnings if necessary. > For each container %c in each server %s in the server group we need to extract the "members" property: > /host=%h/server=%s/subsystem=datagrid-infinispan/cache-container=%c:read-attribute(name=members) > This returns a list of server names (in the form %h:%s). > This is how we should use the information (in combination with the existing "cluster-availability" property information from the coordinator): > 1. If the server-group list coincides with the container members of all nodes, all is good: the cluster is healthy, all nodes are up and running > 2. If all of the container members contain the SAME subset of the server group, but the missing members are in the STOPPED or STARTING state, everything could be normal: we should depend on the coordinator's "cluster-availability" to tell us if the cluster is unhealthy. > 3. If the container members differ between each other and with the server group view, and all these servers are in RUNNING we have a potential split brain or a cluster which is not formed correctly. > The above deduction should determine not only the label / colour-coding we place in the view header (AVAILABLE, DEGRADED, etc) but also some of the view content: in both the cluster nodes view and the cache nodes view we need to group / sort by membership, so that we clearly show split clusters and stopped nodes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6394) Coalesce server group view and Infinispan/JGroups view

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6394?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6394: ---------------------------------- Fix Version/s: 9.0.0.Final 9.0.0.Alpha1 > Coalesce server group view and Infinispan/JGroups view > ------------------------------------------------------ > > Key: ISPN-6394 > URL: https://issues.jboss.org/browse/ISPN-6394 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Critical > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > Currently the console is using the server-group knowledge (i.e. which host/servers belong to a specific group). While that is definitely the "ideal" situation, we also need to ensure that it corresponds to the "actual" cluster as known to Infinispan/JGroups. This information should be then used to present the user with appropriate warnings if necessary. > For each container %c in each server %s in the server group we need to extract the "members" property: > /host=%h/server=%s/subsystem=datagrid-infinispan/cache-container=%c:read-attribute(name=members) > This returns a list of server names (in the form %h:%s). > This is how we should use the information (in combination with the existing "cluster-availability" property information from the coordinator): > 1. If the server-group list coincides with the container members of all nodes, all is good: the cluster is healthy, all nodes are up and running > 2. If all of the container members contain the SAME subset of the server group, but the missing members are in the STOPPED or STARTING state, everything could be normal: we should depend on the coordinator's "cluster-availability" to tell us if the cluster is unhealthy. > 3. If the container members differ between each other and with the server group view, and all these servers are in RUNNING we have a potential split brain or a cluster which is not formed correctly. > The above deduction should determine not only the label / colour-coding we place in the view header (AVAILABLE, DEGRADED, etc) but also some of the view content: in both the cluster nodes view and the cache nodes view we need to group / sort by membership, so that we clearly show split clusters and stopped nodes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6378) Console doesn't scope cache containers to server-groups

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6378?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6378: ---------------------------------- Priority: Critical (was: Major) > Console doesn't scope cache containers to server-groups > ------------------------------------------------------- > > Key: ISPN-6378 > URL: https://issues.jboss.org/browse/ISPN-6378 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > Priority: Critical > Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final > > Attachments: domain-xsite.xml, host-xsite.xml > > > When managing multiple server groups (i.e. clusters), the console doesn't scope cache-containers to the appropriate server-group. > Example: > I have server groups "earth" and "moon", each one declaring a "clustered" cache-container, the console only shows one cache-container ("clustered") whereas it should show two: earth/clustered and moon/clustered > Even with different names, the console is attempting to "resolve" cache-containers against the wrong server-group (possibly the first one). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6421) Instantiation of cache based on template should not modify template

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-6421: ------------------------------------- Summary: Instantiation of cache based on template should not modify template Key: ISPN-6421 URL: https://issues.jboss.org/browse/ISPN-6421 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 8.2.0.Final Reporter: Tristan Tarrant Assignee: Vladimir Blagojevic Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final In cache add, instiating a cache A based on template T should not modify T but should create a configuration A under configurations=CONFIGURATIONS with the "template" attribute set to false and the "configuration" attribute set to T and then a cache A with "configuration" A. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6160) Remove deprecated methods in ProtobufMetadataManager

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6160?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-6160. --------------------------------- Fix Version/s: 8.0.0.Final (was: 9.0.0.Alpha1) Resolution: Done > Remove deprecated methods in ProtobufMetadataManager > ---------------------------------------------------- > > Key: ISPN-6160 > URL: https://issues.jboss.org/browse/ISPN-6160 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management, Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 8.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6205) Remove deprecated methods in ProtobufMetadataManager and ProtobufMetadataManagerMBean

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6205?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-6205. --------------------------------- Resolution: Duplicate Issue > Remove deprecated methods in ProtobufMetadataManager and ProtobufMetadataManagerMBean > ------------------------------------------------------------------------------------- > > Key: ISPN-6205 > URL: https://issues.jboss.org/browse/ISPN-6205 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6159) Remove ClientEvents.addContinuousQueryListener

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6159?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6159: -------------------------------- Fix Version/s: 9.0.0.Final > Remove ClientEvents.addContinuousQueryListener > ---------------------------------------------- > > Key: ISPN-6159 > URL: https://issues.jboss.org/browse/ISPN-6159 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6204) Remove deprecated org.infinispan.query.dsl.QueryBuilder.setProjection

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6204?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6204: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4159 > Remove deprecated org.infinispan.query.dsl.QueryBuilder.setProjection > --------------------------------------------------------------------- > > Key: ISPN-6204 > URL: https://issues.jboss.org/browse/ISPN-6204 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6237) Remove the deprecated InfinispanCollections.emptySet/Map/List

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6237?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6237: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4159 > Remove the deprecated InfinispanCollections.emptySet/Map/List > ------------------------------------------------------------- > > Key: ISPN-6237 > URL: https://issues.jboss.org/browse/ISPN-6237 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2016