February 2020 - infinispan-issues

[JBoss JIRA] (ISPN-11294) CLI allows "cd" below a cache

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11294?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11294: ----------------------------------- Status: Open (was: New) > CLI allows "cd" below a cache > ----------------------------- > > Key: ISPN-11294 > URL: https://issues.redhat.com/browse/ISPN-11294 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 10.1.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11294) CLI allows "cd" below a cache

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11294?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11294: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7851, https://github.com/infinispan/infinispan/pull/7852 > CLI allows "cd" below a cache > ----------------------------- > > Key: ISPN-11294 > URL: https://issues.redhat.com/browse/ISPN-11294 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 10.1.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11294) CLI allows "cd" below a cache

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11294: -------------------------------------- Summary: CLI allows "cd" below a cache Key: ISPN-11294 URL: https://issues.redhat.com/browse/ISPN-11294 Project: Infinispan Issue Type: Bug Components: CLI Affects Versions: 10.1.1.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.1.2.Final, 11.0.0.Alpha1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11293) ResilienceIT should first check if the cluster is stable

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11293?page=com.atlassian.jira.plugi... ] Diego Lovison updated ISPN-11293: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7850 > ResilienceIT should first check if the cluster is stable > -------------------------------------------------------- > > Key: ISPN-11293 > URL: https://issues.redhat.com/browse/ISPN-11293 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.1.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11293) ResilienceIT should first check if the cluster is stable

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11293?page=com.atlassian.jira.plugi... ] Diego Lovison updated ISPN-11293: --------------------------------- Status: Open (was: New) > ResilienceIT should first check if the cluster is stable > -------------------------------------------------------- > > Key: ISPN-11293 > URL: https://issues.redhat.com/browse/ISPN-11293 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.1.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11293) ResilienceIT should first check if the cluster is stable

by Diego Lovison (Jira)

Diego Lovison created ISPN-11293: ------------------------------------ Summary: ResilienceIT should first check if the cluster is stable Key: ISPN-11293 URL: https://issues.redhat.com/browse/ISPN-11293 Project: Infinispan Issue Type: Bug Affects Versions: 10.1.1.Final Reporter: Diego Lovison -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11293) ResilienceIT should first check if the cluster is stable

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11293?page=com.atlassian.jira.plugi... ] Diego Lovison reassigned ISPN-11293: ------------------------------------ Assignee: Diego Lovison > ResilienceIT should first check if the cluster is stable > -------------------------------------------------------- > > Key: ISPN-11293 > URL: https://issues.redhat.com/browse/ISPN-11293 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.1.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11245) default logging is with simplified classnames "c{1}" but full names are expected

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11245?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11245: ----------------------------------- Fix Version/s: 10.1.2.Final > default logging is with simplified classnames "c{1}" but full names are expected > -------------------------------------------------------------------------------- > > Key: ISPN-11245 > URL: https://issues.redhat.com/browse/ISPN-11245 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Major > Fix For: 10.1.2.Final, 11.0.0.Alpha1 > > > It will be confusing if the class names are not fully shown because > - not clear which part is logging (jgroups, infinispan, custom classes) > - infinispan classes might be not unique > - application classes might use similar names to infinispan > - application classes might not have unique names > For this the full category should be shown as before -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11266) Split CacheTopologyControlCommand into individual commands

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11266?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11266: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7849 > Split CacheTopologyControlCommand into individual commands > ---------------------------------------------------------- > > Key: ISPN-11266 > URL: https://issues.redhat.com/browse/ISPN-11266 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Alpha1 > > > Currently the {{CacheTopologyControlCommand}} uses a Type field and a switch statement to differentiate between various topology actions. This worked well for the old Externalizer approach, however it does not fit well with protobuf messages. Instead, the CacheTopologyControlCommand should be split into individual commands, e.g. a TopologyJoinCommand etc. > This enables the logic of the command types to be separated, making it easier to maintain backwards compatibility in the long term. Each command will use a ProtoStream TypeId in the range of 1000 -> 3999, so the cost of two bytes is the same as the existing class ID plus enum Type that we require with the single CacheTopologyControlCommand. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11292) Add in (non)blocking thread pools

by Will Burns (Jira)

Will Burns created ISPN-11292: --------------------------------- Summary: Add in (non)blocking thread pools Key: ISPN-11292 URL: https://issues.redhat.com/browse/ISPN-11292 Project: Infinispan Issue Type: Sub-task Components: Core Reporter: Will Burns Assignee: Will Burns We should remove the ASYNC_OPERATIONS_EXECUTOR and PERSISTENCE_EXECUTOR components and replace them with a NON_BLOCKING_EXECUTOR and BLOCKING_EXECUTOR or something similarly named. We should probably default the NON_BLOCKING_EXECUTOR to 2 * numCPU and blocking to 100? The queue size should be a bit bigger for blocking as compared to non blocking. The parser should allow these to be changed as other executors are currently. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2020