July 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10382) Document Queries for Health Check API in Domain Mode

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10382?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10382: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7116, https://github.com/infinispan/infinispan/pull/7117, https://github.com/infinispan/infinispan/pull/7128, https://github.com/infinispan/infinispan/pull/7129 (was: https://github.com/infinispan/infinispan/pull/7116, https://github.com/infinispan/infinispan/pull/7117) > Document Queries for Health Check API in Domain Mode > ---------------------------------------------------- > > Key: ISPN-10382 > URL: https://issues.jboss.org/browse/ISPN-10382 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Affects Versions: 10.0.0.Beta3, 9.4.15.Final > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.16.Final > > > Update docs with health check API queries in domain mode. This issue documents JDG-2985. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10392) Support cache creation with template via REST

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10392?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10392: ------------------------------------- Status: Open (was: New) > Support cache creation with template via REST > --------------------------------------------- > > Key: ISPN-10392 > URL: https://issues.jboss.org/browse/ISPN-10392 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10392) Support cache creation with template via REST

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10392?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10392: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7127 > Support cache creation with template via REST > --------------------------------------------- > > Key: ISPN-10392 > URL: https://issues.jboss.org/browse/ISPN-10392 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10392) Support cache creation with template via REST

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10392: ---------------------------------------- Summary: Support cache creation with template via REST Key: ISPN-10392 URL: https://issues.jboss.org/browse/ISPN-10392 Project: Infinispan Issue Type: Feature Request Components: REST Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10391) Possible loss of (pessimistic) lock if the lock owner is expelled from the cluster and merged later

by Wolf-Dieter Fink (Jira)

[ https://issues.jboss.org/browse/ISPN-10391?page=com.atlassian.jira.plugin... ] Wolf-Dieter Fink commented on ISPN-10391: ----------------------------------------- To prevent from this the pessimistic locking transaction need to be changed from one-phase-commit to two-phase-commit, which is 2 times slower by committing the Tx, since the backup owner(s) don't have locks and can't make any decision on their own. As this would affect the consistency with the drawback of performance the default should prefer consistency but it should be possible to switch back to the old behaviour by configuration. > Possible loss of (pessimistic) lock if the lock owner is expelled from the cluster and merged later > --------------------------------------------------------------------------------------------------- > > Key: ISPN-10391 > URL: https://issues.jboss.org/browse/ISPN-10391 > Project: Infinispan > Issue Type: Enhancement > Components: API > Reporter: Wolf-Dieter Fink > Priority: Major > > In case of pessimistic locking the lock is freed if the lock-owner is expelled from the cluster. > The cluster is able to get a lock for the entry even if the original lock-owner is still alive (but not longer a member of the cluster) > In this case there is a possibility for an inconsistency after the cluster is merged. > The two scenarios are > 1) one or more nodes are disconnected to the others by network issues > 2) one node is blocked by a full GC ( or suspended for another reason) > The first case must be handled by enable partition handling and set a merge policy to solve the conflict. > The second one is not handled by partition handling and here it is possible that the remaining cluster will get the lock and changed the entry until the original owner is merged back, and due to the 'stop the world' pause continue and change the entry based on the old state without failure - and this will cause unexpected inconsistent results. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10391) Possible loss of (pessimistic) lock if the lock owner is expelled from the cluster and merged later

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10391: --------------------------------------- Summary: Possible loss of (pessimistic) lock if the lock owner is expelled from the cluster and merged later Key: ISPN-10391 URL: https://issues.jboss.org/browse/ISPN-10391 Project: Infinispan Issue Type: Enhancement Components: API Reporter: Wolf-Dieter Fink In case of pessimistic locking the lock is freed if the lock-owner is expelled from the cluster. The cluster is able to get a lock for the entry even if the original lock-owner is still alive (but not longer a member of the cluster) In this case there is a possibility for an inconsistency after the cluster is merged. The two scenarios are 1) one or more nodes are disconnected to the others by network issues 2) one node is blocked by a full GC ( or suspended for another reason) The first case must be handled by enable partition handling and set a merge policy to solve the conflict. The second one is not handled by partition handling and here it is possible that the remaining cluster will get the lock and changed the entry until the original owner is merged back, and due to the 'stop the world' pause continue and change the entry based on the old state without failure - and this will cause unexpected inconsistent results. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9942) Cache Configuration resource

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9942?page=com.atlassian.jira.plugin.... ] Work on ISPN-9942 started by Gustavo Fernandes. ----------------------------------------------- > Cache Configuration resource > ---------------------------- > > Key: ISPN-9942 > URL: https://issues.jboss.org/browse/ISPN-9942 > Project: Infinispan > Issue Type: Sub-task > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > As part of https://issues.jboss.org/browse/ISPN-9771, an initial resource to manager cache configuration was added, in "read-only" mode: > {code} > GET /v2/configurations/{name} > POST /v2/configurations?action=toJSON > {code} > This should be extended to allow: > * Creating a new cache configuration > * Deleting a configuration -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9942) Cache Configuration resource

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9942?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9942: ------------------------------------ Status: Open (was: New) > Cache Configuration resource > ---------------------------- > > Key: ISPN-9942 > URL: https://issues.jboss.org/browse/ISPN-9942 > Project: Infinispan > Issue Type: Sub-task > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > As part of https://issues.jboss.org/browse/ISPN-9771, an initial resource to manager cache configuration was added, in "read-only" mode: > {code} > GET /v2/configurations/{name} > POST /v2/configurations?action=toJSON > {code} > This should be extended to allow: > * Creating a new cache configuration > * Deleting a configuration -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10152) REST counter admin

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10152?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10152: ------------------------------------- Status: Open (was: New) > REST counter admin > ------------------ > > Key: ISPN-10152 > URL: https://issues.jboss.org/browse/ISPN-10152 > Project: Infinispan > Issue Type: Sub-task > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10152) REST counter admin

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10152?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10152: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7125 > REST counter admin > ------------------ > > Key: ISPN-10152 > URL: https://issues.jboss.org/browse/ISPN-10152 > Project: Infinispan > Issue Type: Sub-task > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 July 2019