April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11721) Add Rolling Upgrade CLI commands

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11721?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11721: ----------------------------------- Description: The CLI should be able to invoke the rolling upgrade commands exposed in ISPN-11503 The commands should be: {{migrate connect cachename sourceaddress}} {{migrate synchronize cachename}} {{migrate disconnect cachename}} The {{connect}} subcommand should probably take a {{hotrod-client.properties}} file which contains connection information (e.g. security, etc) We should also support full server migration (i.e. without specifying the cache), as well as implementing ISPN-1407 was: The CLI should be able to invoke the rolling upgrade commands exposed in ISPN-11503 The commands should be: {{migrate connect cachename sourceaddress}} {{migrate synchronize cachename}} {{migrate disconnect cachename}} The {{connect}} subcommand should probably take a {{hotrod-client.properties}} file which contains connection information (e.g. security, etc) > Add Rolling Upgrade CLI commands > -------------------------------- > > Key: ISPN-11721 > URL: https://issues.redhat.com/browse/ISPN-11721 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Affects Versions: 11.0.0.Dev04 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > The CLI should be able to invoke the rolling upgrade commands exposed in ISPN-11503 > The commands should be: > {{migrate connect cachename sourceaddress}} > {{migrate synchronize cachename}} > {{migrate disconnect cachename}} > The {{connect}} subcommand should probably take a {{hotrod-client.properties}} file which contains connection information (e.g. security, etc) > We should also support full server migration (i.e. without specifying the cache), as well as implementing ISPN-1407 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11721) Add Rolling Upgrade CLI commands

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11721?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11721: ----------------------------------- Description: The CLI should be able to invoke the rolling upgrade commands exposed in ISPN-11503 The commands should be: {{migrate connect cachename sourceaddress}} {{migrate synchronize cachename}} {{migrate disconnect cachename}} The {{connect}} subcommand should probably take a {{hotrod-client.properties}} file which contains connection information (e.g. security, etc) was: The CLI should be able to invoke the rolling upgrade commands exposed in ISPN-11503 The commands should be: `migrate connect cachename sourceaddress` `migrate synchronize cachename` `migrate disconnect cachename` > Add Rolling Upgrade CLI commands > -------------------------------- > > Key: ISPN-11721 > URL: https://issues.redhat.com/browse/ISPN-11721 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Affects Versions: 11.0.0.Dev04 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > The CLI should be able to invoke the rolling upgrade commands exposed in ISPN-11503 > The commands should be: > {{migrate connect cachename sourceaddress}} > {{migrate synchronize cachename}} > {{migrate disconnect cachename}} > The {{connect}} subcommand should probably take a {{hotrod-client.properties}} file which contains connection information (e.g. security, etc) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11721) Add Rolling Upgrade CLI commands

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11721: -------------------------------------- Summary: Add Rolling Upgrade CLI commands Key: ISPN-11721 URL: https://issues.redhat.com/browse/ISPN-11721 Project: Infinispan Issue Type: Enhancement Components: CLI Affects Versions: 11.0.0.Dev04 Reporter: Tristan Tarrant Assignee: Tristan Tarrant The CLI should be able to invoke the rolling upgrade commands exposed in ISPN-11503 The commands should be: `migrate connect cachename sourceaddress` `migrate synchronize cachename` `migrate disconnect cachename` -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11720) Add support for non blocking counter listeners

by Will Burns (Jira)

Will Burns created ISPN-11720: --------------------------------- Summary: Add support for non blocking counter listeners Key: ISPN-11720 URL: https://issues.redhat.com/browse/ISPN-11720 Project: Infinispan Issue Type: Feature Request Components: Clustered Counter Reporter: Will Burns Assignee: Pedro Ruivo The current counter notifications are done in a blocking fashion and thus we must invoke these on the blocking thread. It would be beneficial if instead we allow the user to have a listener that is non blocking and invoke the notifications in the non blocking thread. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11697) Server Docs: Fix user tool issues

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11697?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11697: ------------------------------- Sprint: DataGrid Sprint #43 > Server Docs: Fix user tool issues > --------------------------------- > > Key: ISPN-11697 > URL: https://issues.redhat.com/browse/ISPN-11697 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > 11/master: needs to be user-tool not user-tools. add missing + characters to keep things together in rendered html > 10.1.x: According to the following documentation [1] of user-tools, '-a' is includedd in example command line. > But when invoking user-tools with '-a', that throws ISPN090001. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11479) Enforce <indexed-entities> for protobuf payloads in indexed caches

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11479?page=com.atlassian.jira.plugi... ] Work on ISPN-11479 started by Nistor Adrian. -------------------------------------------- > Enforce <indexed-entities> for protobuf payloads in indexed caches > ------------------------------------------------------------------ > > Key: ISPN-11479 > URL: https://issues.redhat.com/browse/ISPN-11479 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Final, 11.0.0.Dev05 > > > This config element must have the same meaning as for indexed classes. > It must list FQNs of indexed types. > <indexed-entities> occurence must also be set to 1..n in xsd -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11479) Enforce <indexed-entities> for protobuf payloads in indexed caches

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11479?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11479: --------------------------------- Fix Version/s: 11.0.0.Dev05 > Enforce <indexed-entities> for protobuf payloads in indexed caches > ------------------------------------------------------------------ > > Key: ISPN-11479 > URL: https://issues.redhat.com/browse/ISPN-11479 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Final, 11.0.0.Dev05 > > > This config element must have the same meaning as for indexed classes. > It must list FQNs of indexed types. > <indexed-entities> occurence must also be set to 1..n in xsd -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11719) Deprecate ConsistentHashFactory customization

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-11719: --------------------------------------- Summary: Deprecate ConsistentHashFactory customization Key: ISPN-11719 URL: https://issues.redhat.com/browse/ISPN-11719 Project: Infinispan Issue Type: Task Components: Configuration, Core Affects Versions: 11.0.0.Dev04 Reporter: Wolf-Dieter Fink Assignee: Dan Berindei Fix For: 11.0.0.Final, 11.0.0.Dev05 There aren't any good reasons to use a {{ConsistentHashFactory}} implementation different than the default selected by {{StateTransferManagerImpl#pickConsistentHashFactory}}. The configuration attribute made sense when the default was {{DefaultConsistentHashFactory}}, but {{SyncConsistentHashFactory}} is much better nowadays, and it's pretty much impossible to come up with an implementation that works in more than one cache mode with the current API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11718) Conflict resolution cannot be cancelled

by Dan Berindei (Jira)

Dan Berindei created ISPN-11718: ----------------------------------- Summary: Conflict resolution cannot be cancelled Key: ISPN-11718 URL: https://issues.redhat.com/browse/ISPN-11718 Project: Infinispan Issue Type: Bug Components: Core, State Transfer Affects Versions: 10.1.6.Final, 11.0.0.Dev04 Reporter: Dan Berindei {{DefaultConflictManager.cancelConflictResolution()}} has no effect, because it completes a {{CompletableFuture}} but it does not actually stop the iteration over conflicts. Luckily it's only used when the cache is down to a single node, which would make the conflict resolution much faster anyway, so it's not critical. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11717) Deprecate ConsistentHashFactory customization

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11717?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11717: -------------------------------- Status: Open (was: New) > Deprecate ConsistentHashFactory customization > --------------------------------------------- > > Key: ISPN-11717 > URL: https://issues.redhat.com/browse/ISPN-11717 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 11.0.0.Dev04 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final, 11.0.0.Dev05 > > > There aren't any good reasons to use a {{ConsistentHashFactory}} implementation different than the default selected by {{StateTransferManagerImpl#pickConsistentHashFactory}}. > The configuration attribute made sense when the default was {{DefaultConsistentHashFactory}}, but {{SyncConsistentHashFactory}} is much better nowadays, and it's pretty much impossible to come up with an implementation that works in more than one cache mode with the current API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2020