September 2020 - infinispan-issues

[JBoss JIRA] (IPROTO-161) Maven compiler plugin 2.8.1 and Protostream seem broken

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ] Katia Aresti updated IPROTO-161: -------------------------------- Priority: Blocker (was: Major) > Maven compiler plugin 2.8.1 and Protostream seem broken > ------------------------------------------------------- > > Key: IPROTO-161 > URL: https://issues.redhat.com/browse/IPROTO-161 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.3.Final > Reporter: Katia Aresti > Assignee: Nistor Adrian > Priority: Blocker > > Coming from a Quarkus issue, from maven compiler plugin 2.8.1 seems not working properly with classes compilation and generation > > Check the Quarkus issue. > > https://github.com/quarkusio/quarkus/issues/9980 > > This might be a library problem or a maven problem > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-161) Maven compiler plugin 2.8.1 and Protostream seem broken

by Katia Aresti (Jira)

Katia Aresti created IPROTO-161: ----------------------------------- Summary: Maven compiler plugin 2.8.1 and Protostream seem broken Key: IPROTO-161 URL: https://issues.redhat.com/browse/IPROTO-161 Project: Infinispan ProtoStream Issue Type: Bug Affects Versions: 4.3.3.Final Reporter: Katia Aresti Assignee: Nistor Adrian Coming from a Quarkus issue, from maven compiler plugin 2.8.1 seems not working properly with classes compilation and generation Check the Quarkus issue. This might be a library problem or a maven problem -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-161) Maven compiler plugin 2.8.1 and Protostream seem broken

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ] Katia Aresti updated IPROTO-161: -------------------------------- Description: Coming from a Quarkus issue, from maven compiler plugin 2.8.1 seems not working properly with classes compilation and generation Check the Quarkus issue. https://github.com/quarkusio/quarkus/issues/9980 This might be a library problem or a maven problem was: Coming from a Quarkus issue, from maven compiler plugin 2.8.1 seems not working properly with classes compilation and generation Check the Quarkus issue. This might be a library problem or a maven problem > Maven compiler plugin 2.8.1 and Protostream seem broken > ------------------------------------------------------- > > Key: IPROTO-161 > URL: https://issues.redhat.com/browse/IPROTO-161 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.3.Final > Reporter: Katia Aresti > Assignee: Nistor Adrian > Priority: Major > > Coming from a Quarkus issue, from maven compiler plugin 2.8.1 seems not working properly with classes compilation and generation > > Check the Quarkus issue. > > https://github.com/quarkusio/quarkus/issues/9980 > > This might be a library problem or a maven problem > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10737) Operator Docs: Choose working profiles for DG clusters

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10737?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10737. ------------------------------ Resolution: Out of Date > Operator Docs: Choose working profiles for DG clusters > ------------------------------------------------------ > > Key: ISPN-10737 > URL: https://issues.redhat.com/browse/ISPN-10737 > Project: Infinispan > Issue Type: Task > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > https://github.com/infinispan/infinispan-operator/issues/128 > https://github.com/infinispan/infinispan-operator/issues/132 > https://github.com/infinispan/infinispan-operator/issues/133 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12224) Cluster in a confusing state after restarted from graceful shutdown - no hint for waiting on complete restarted

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-12224?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez reassigned ISPN-12224: --------------------------------------------- Assignee: Dan Berindei > Cluster in a confusing state after restarted from graceful shutdown - no hint for waiting on complete restarted > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-12224 > URL: https://issues.redhat.com/browse/ISPN-12224 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 12.0.0.Dev01, 11.0.3.Final > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Priority: Critical > > After a cluster is stopped with "shutdown cluster" and incomplete restart there is no WARN or INFO message that the cluster is in an incomplete state if not all nodes are back. > If there is a single node started it is still possible to add new entries!! > As well as entries can be read. > But the server will throw Exceptions. > The expectation is to have log messages with a statement that the cluster of (a,b, ...) is incomplete started after graceful shutdown and the missing nodes are (x,y,...) > It should not be possible to access caches. > There should be a CLI/JMX option to interrupt the graceful start and set the cluster to a working state - even if there is a possible loss of data in this case. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12349) Eviction <memory> attribute when-full does not work as expected

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-12349?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-12349: ------------------------------------ Affects Version/s: 11.0.3.Final > Eviction <memory> attribute when-full does not work as expected > --------------------------------------------------------------- > > Key: ISPN-12349 > URL: https://issues.redhat.com/browse/ISPN-12349 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 12.0.0.Dev03, 11.0.3.Final > Reporter: Wolf-Dieter Fink > Priority: Major > > Eviction can be configured with the <memory> element and use when-full of NONE|MANUAL|REMOVE|EXCEPTION > From XSD: > NONE - Do not evict entries. ... > MANUAL Manually evict entries. This strategy is the same as NONE but does not log errors if you enable passivation without eviction. > REMOVE - Automatically evict older entries to make space for new entries. By default REMOVE is always used when you define a size for the data container unless you configure the EXCEPTION strategy. > EXCEPTION Do not evict entries. If the data container reaches the maximum size, exceptions occur for requests to create new entries. > With a store (here RocksDB) no matter whether passivation is enabled or not > EXCEPTION will NOT throw an Exception but does not evict any entry, the entries can be added with the drawback that the statistic is wrong num-in-mem=X current-num-entries=X total-entires=0 > -> without a store the Exception is thrown as expected > With REMOVE the eviction will work as expected > NONE|MANUAL will default always to REMOVE and not show the behavior in its description no matter whether a store and passivation is used. > NONE and MANUAL seems useless and lead confusion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12349) Eviction <memory> attribute when-full does not work as expected

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-12349?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-12349: ------------------------------------ Affects Version/s: 12.0.0.Dev03 > Eviction <memory> attribute when-full does not work as expected > --------------------------------------------------------------- > > Key: ISPN-12349 > URL: https://issues.redhat.com/browse/ISPN-12349 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 12.0.0.Dev03 > Reporter: Wolf-Dieter Fink > Priority: Major > > Eviction can be configured with the <memory> element and use when-full of NONE|MANUAL|REMOVE|EXCEPTION > From XSD: > NONE - Do not evict entries. ... > MANUAL Manually evict entries. This strategy is the same as NONE but does not log errors if you enable passivation without eviction. > REMOVE - Automatically evict older entries to make space for new entries. By default REMOVE is always used when you define a size for the data container unless you configure the EXCEPTION strategy. > EXCEPTION Do not evict entries. If the data container reaches the maximum size, exceptions occur for requests to create new entries. > With a store (here RocksDB) no matter whether passivation is enabled or not > EXCEPTION will NOT throw an Exception but does not evict any entry, the entries can be added with the drawback that the statistic is wrong num-in-mem=X current-num-entries=X total-entires=0 > -> without a store the Exception is thrown as expected > With REMOVE the eviction will work as expected > NONE|MANUAL will default always to REMOVE and not show the behavior in its description no matter whether a store and passivation is used. > NONE and MANUAL seems useless and lead confusion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12349) Eviction <memory> attribute when-full does not work as expected

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12349: --------------------------------------- Summary: Eviction <memory> attribute when-full does not work as expected Key: ISPN-12349 URL: https://issues.redhat.com/browse/ISPN-12349 Project: Infinispan Issue Type: Bug Components: Core Reporter: Wolf-Dieter Fink Eviction can be configured with the <memory> element and use when-full of NONE|MANUAL|REMOVE|EXCEPTION From XSD: NONE - Do not evict entries. ... MANUAL Manually evict entries. This strategy is the same as NONE but does not log errors if you enable passivation without eviction. REMOVE - Automatically evict older entries to make space for new entries. By default REMOVE is always used when you define a size for the data container unless you configure the EXCEPTION strategy. EXCEPTION Do not evict entries. If the data container reaches the maximum size, exceptions occur for requests to create new entries. With a store (here RocksDB) no matter whether passivation is enabled or not EXCEPTION will NOT throw an Exception but does not evict any entry, the entries can be added with the drawback that the statistic is wrong num-in-mem=X current-num-entries=X total-entires=0 -> without a store the Exception is thrown as expected With REMOVE the eviction will work as expected NONE|MANUAL will default always to REMOVE and not show the behavior in its description no matter whether a store and passivation is used. NONE and MANUAL seems useless and lead confusion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12311) Data access pizza chart show invalid percent value

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12311?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12311: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.4.Final 12.0.0.Dev04 Resolution: Done > Data access pizza chart show invalid percent value > -------------------------------------------------- > > Key: ISPN-12311 > URL: https://issues.redhat.com/browse/ISPN-12311 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 11.0.4.Final, 12.0.0.Dev04 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12224) Cluster in a confusing state after restarted from graceful shutdown - no hint for waiting on complete restarted

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-12224?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink commented on ISPN-12224: ----------------------------------------- As discussed the behavior should be to reject client access and do no rebalancing until all the former known cluster nodes are back and ready (might be loaded from persistence). After this there is no need for rebalancing as the state and data distribution is the same as before. From now on the cluster will act as normal and up- downscaling is possible and will trigger a rebalancing > Cluster in a confusing state after restarted from graceful shutdown - no hint for waiting on complete restarted > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-12224 > URL: https://issues.redhat.com/browse/ISPN-12224 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 12.0.0.Dev01, 11.0.3.Final > Reporter: Wolf-Dieter Fink > Priority: Critical > > After a cluster is stopped with "shutdown cluster" and incomplete restart there is no WARN or INFO message that the cluster is in an incomplete state if not all nodes are back. > If there is a single node started it is still possible to add new entries!! > As well as entries can be read. > But the server will throw Exceptions. > The expectation is to have log messages with a statement that the cluster of (a,b, ...) is incomplete started after graceful shutdown and the missing nodes are (x,y,...) > It should not be possible to access caches. > There should be a CLI/JMX option to interrupt the graceful start and set the cluster to a working state - even if there is a possible loss of data in this case. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2020