September 2020 - infinispan-issues

[JBoss JIRA] (ISPN-11412) Documentation for the console

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11412?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11412. ------------------------------ Resolution: Out of Date > Documentation for the console > ----------------------------- > > Key: ISPN-11412 > URL: https://issues.redhat.com/browse/ISPN-11412 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation > Affects Versions: 10.1.3.Final > Reporter: Katia Aresti > Assignee: Donald Naro > Priority: Major > Labels: console-ng > Attachments: screenshot-1.png > > > Currently the documentation of the web console does not exist. > The current console is very simple but it should be listed in > https://infinispan.org/docs/stable/index.html > at this point. > Some screenshots and a couple of features could be nice to be explained. > Not much needed at this point -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11412) Documentation for the console

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11412?page=com.atlassian.jira.plugi... ] Donald Naro reopened ISPN-11412: -------------------------------- > Documentation for the console > ----------------------------- > > Key: ISPN-11412 > URL: https://issues.redhat.com/browse/ISPN-11412 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation > Affects Versions: 10.1.3.Final > Reporter: Katia Aresti > Assignee: Donald Naro > Priority: Major > Labels: console-ng > Attachments: screenshot-1.png > > > Currently the documentation of the web console does not exist. > The current console is very simple but it should be listed in > https://infinispan.org/docs/stable/index.html > at this point. > Some screenshots and a couple of features could be nice to be explained. > Not much needed at this point -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12350) Persistent UUIDs are only used for initial consistent hash

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12350?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12350: -------------------------------- Status: Open (was: New) > Persistent UUIDs are only used for initial consistent hash > ---------------------------------------------------------- > > Key: ISPN-12350 > URL: https://issues.redhat.com/browse/ISPN-12350 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 12.0.0.Dev03, 11.0.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final > > > After a graceful restart, the persisted UUIDs are used to re-create the consistent hash of the cache before shutdown. This initial CH will not be rebalanced, so there is no state transfer immediately after cluster restart. > However, if something then triggers a rebalance (e.g. a node join/leave), the persistent UUIDs are ignored, and {{SyncConsistentHashFactory}} allocates segments based on the new JGroups addresses instead of the persistent UUIDs. > I modified {{ThreeNodeDistGlobalStateRestartTest}} to force a rebalance after restart, and I got > {noformat} > 11:24:07,424 TRACE (jgroups-7,Test-NodeD:[]) [ClusterCacheStatus] Cache testCache topology updated: CacheTopology{id=1, phase=NO_REBALANCE, rebalanceId=1, currentCH=DefaultConsistentHash{ns=256, owners = (3)[Test-NodeD: 83+0, Test-NodeE: 87+0, Test-NodeF: 86+0]}, pendingCH=null, unionCH=null, actualMembers=[Test-NodeD, Test-NodeE, Test-NodeF], persistentUUIDs=[1ba71c04-a6b9-4a5c-9f51-e5e358081dc6, 6d3ff549-aafa-4d8a-8617-84ac6f119549, f37f6a8c-32a4-4dda-b1b0-876c24f42c6a]}, members = [Test-NodeD, Test-NodeE, Test-NodeF], joiners = [] > 11:24:07,889 TRACE (testng-Test:[]) [ClusterCacheStatus] Rebalancing consistent hash for cache testCache, members are [Test-NodeD, Test-NodeE, Test-NodeF] > 11:24:07,909 TRACE (testng-Test:[]) [ClusterCacheStatus] Updating cache testCache topology for rebalance: CacheTopology{id=2, phase=READ_OLD_WRITE_ALL, rebalanceId=2, currentCH=DefaultConsistentHash{ns=256, owners = (3)[Test-NodeD: 83+0, Test-NodeE: 87+0, Test-NodeF: 86+0]}, pendingCH=DefaultConsistentHash{ns=256, owners = (3)[Test-NodeD: 87+0, Test-NodeE: 83+0, Test-NodeF: 86+0]}, unionCH=null, actualMembers=[Test-NodeD, Test-NodeE, Test-NodeF], persistentUUIDs=[1ba71c04-a6b9-4a5c-9f51-e5e358081dc6, 6d3ff549-aafa-4d8a-8617-84ac6f119549, f37f6a8c-32a4-4dda-b1b0-876c24f42c6a]} > 11:24:07,910 TRACE (testng-Test:[]) [ClusterCacheStatus] Moved segments: [Test-NodeD added 72 removed 68, Test-NodeE added 49 removed 53, Test-NodeF added 59 removed 59] > {noformat} > This issue does not affect caches using {{DefaultConsistentHashFactory}}, because it doesn't care about member UUIDs. Since there is no {{SyncScatteredConsistentHashFactory}}, scattered cache are not affected at all. Replicated caches with the default {{SyncReplicateedConsistentHashFactory}} will change primary owners, but they won't need any state transfer. > {{TestingUtil.waitForNoRebalance()}} works around the issue by not checking whether the initial consistent hash (with topologyId==1) is balanced. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10625) Documentation should have all topics in one document

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10625?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10625. ------------------------------ Resolution: Out of Date We've added search to the docs home page. > Documentation should have all topics in one document > ---------------------------------------------------- > > Key: ISPN-10625 > URL: https://issues.redhat.com/browse/ISPN-10625 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 10.0.0.CR2 > Reporter: Diego Lovison > Assignee: Donald Naro > Priority: Major > > As a developer, I would like to search for a method or class name in a single doc. It will speed up my research. Today I need to open all guides and search. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10598) Docs: Embedded Security Guide

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10598?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10598. ------------------------------ Resolution: Out of Date > Docs: Embedded Security Guide > ----------------------------- > > Key: ISPN-10598 > URL: https://issues.redhat.com/browse/ISPN-10598 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12351) ImmutableListCopy makes too many copies

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12351?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12351: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8711 > ImmutableListCopy makes too many copies > --------------------------------------- > > Key: ISPN-12351 > URL: https://issues.redhat.com/browse/ISPN-12351 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 12.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 12.0.0.Dev04 > > > An array copy is not needed when creating a new {{ImmutableListCopy}} instance from another {{ImmutableListCopy}}. > The constructor with 2 list parameters can also avoid one array allocation by pre-allocating the array, or by using one list's array when the other list is empty. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12221) Add zero-capacity-node support for Replicated caches

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12221?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12221: -------------------------------- Status: Open (was: New) > Add zero-capacity-node support for Replicated caches > ---------------------------------------------------- > > Key: ISPN-12221 > URL: https://issues.redhat.com/browse/ISPN-12221 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 12.0.0.Dev01 > Reporter: Ryan Emerson > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Dev04 > > > Currently if a container is configured to have {{zero-capacity-node=true}} this only applies to distributed caches. To prevent state-transfer for replicated caches, we should modify {{ReplicatedConsistentHashFactory}} and {{ReplicatedConsistentHash}} to allow a node to be a member without also being an owner. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12221) Add zero-capacity-node support for Replicated caches

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12221?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12221: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8711 > Add zero-capacity-node support for Replicated caches > ---------------------------------------------------- > > Key: ISPN-12221 > URL: https://issues.redhat.com/browse/ISPN-12221 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 12.0.0.Dev01 > Reporter: Ryan Emerson > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Dev04 > > > Currently if a container is configured to have {{zero-capacity-node=true}} this only applies to distributed caches. To prevent state-transfer for replicated caches, we should modify {{ReplicatedConsistentHashFactory}} and {{ReplicatedConsistentHash}} to allow a node to be a member without also being an owner. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12353) REST allow backup restore progress to be submitted and polled

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12353?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-12353: -------------------------------- Description: The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: {code} # Create, return 202 or 409 if {restoreName} already exists POST /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} # Poll progress 201 complete, 202 if in progress, or 404 if not found HEAD /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} {code} was: The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: {code} # Create, return 202 or 409 if \{restoreName} already exists POST /rest/v2/cache-managers/\{cacheManagerName}/restores/\{restoreName} # Poll progress 201 complete, 202 if in progress, or 404 if not found HEAD /rest/v2/cache-managers/ {cacheManagerName}/restores/{restoreName} {code} > REST allow backup restore progress to be submitted and polled > ------------------------------------------------------------- > > Key: ISPN-12353 > URL: https://issues.redhat.com/browse/ISPN-12353 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 12.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: > {code} > # Create, return 202 or 409 if {restoreName} already exists > POST /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} > # Poll progress 201 complete, 202 if in progress, or 404 if not found > HEAD /rest/v2/cache-managers/{cacheManagerName}/restores/{restoreName} > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12353) REST allow backup restore progress to be submitted and polled

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-12353?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-12353: -------------------------------- Description: The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: {code} # Create, return 202 or 409 if \{restoreName} already exists POST /rest/v2/cache-managers/\{cacheManagerName}/restores/\{restoreName} # Poll progress 201 complete, 202 if in progress, or 404 if not found HEAD /rest/v2/cache-managers/ {cacheManagerName}/restores/{restoreName} {code} was: The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: ``` # Create, return 202 or 409 if \{restoreName} already exists POST /rest/v2/cache-managers/\{cacheManagerName}/restores/\{restoreName} # Poll progress 201 complete, 202 if in progress, or 404 if not found HEAD /rest/v2/cache-managers/ \{cacheManagerName} /restores/ {restoreName} ``` > REST allow backup restore progress to be submitted and polled > ------------------------------------------------------------- > > Key: ISPN-12353 > URL: https://issues.redhat.com/browse/ISPN-12353 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 12.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Final > > > The current rest endpoint for restoring backups is too restrictive, as there is no way to submit a restoration and then poll it's current status. We should add the following so that the endpoints are akin to the process for creating a backup: > {code} > # Create, return 202 or 409 if \{restoreName} already exists > POST /rest/v2/cache-managers/\{cacheManagerName}/restores/\{restoreName} > # Poll progress 201 complete, 202 if in progress, or 404 if not found > HEAD /rest/v2/cache-managers/ {cacheManagerName}/restores/{restoreName} > {code} -- 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