[JBoss JIRA] (ISPN-11815) Elytron 1.11.4.Final
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11815?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11815:
-----------------------------------
Sprint: DataGrid Sprint #44, DataGrid Sprint #45 (was: DataGrid Sprint #44)
> Elytron 1.11.4.Final
> --------------------
>
> Key: ISPN-11815
> URL: https://issues.redhat.com/browse/ISPN-11815
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Security
> Affects Versions: 11.0.0.Dev05, 10.1.8.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> The granular elytron dependencies are currently causing issues with some of the mechs in the client (SCRAM and GS2). We should use the combined wildfly-elytron jar.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11802) Create SPI for Cross-Site Replication conflict resolution
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11802?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11802:
-----------------------------------
Sprint: DataGrid Sprint #44, DataGrid Sprint #45 (was: DataGrid Sprint #44)
> Create SPI for Cross-Site Replication conflict resolution
> ---------------------------------------------------------
>
> Key: ISPN-11802
> URL: https://issues.redhat.com/browse/ISPN-11802
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Cross-Site Replication
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
>
> A conflict happens if 2 sites try to update the same key (put/remove) concurrently.
> With async Cross-Site Replication (aka IRAC) when a conflict is detected, we use the site name to pick the winning update.
> h2. Interface
> {code:java}
> interface ABC<V> { // or concrete class
> String site(); //the site name which wrote this value
> V value(); // the value. can be null if the key was removed
> Metadata metadata(); //can be null
> }
> interface Resolve<K, V> {
> ABC<V> resolve(K key, ABC<V> entry1, ABC<V> entry2);
> }
> {code}
> h2. Configuration
> Set the class name to use. Can be a {{Class}} object (as shown above) or a {{String}} with the class name.
> For server mode, you need to add your jar with the classes required to {{server/lib}}.
> The configuration fails to validate if the conflict resolution class is set with {{SYNC}} strategy.
> {code:java}
> ConfigurationBuilder.sites().addBackup()
> .site("S")
> .strategy(BackupConfiguration.BackupStrategy.ASYNC)
> .conflictResolution(MyResover.class);
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11851) FD_SOCK should use the same bind address as TCP
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11851?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11851:
-----------------------------------
Sprint: DataGrid Sprint #44, DataGrid Sprint #45 (was: DataGrid Sprint #44)
> FD_SOCK should use the same bind address as TCP
> -----------------------------------------------
>
> Key: ISPN-11851
> URL: https://issues.redhat.com/browse/ISPN-11851
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 11.0.0.Dev05, 10.1.8.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> In the JGroups configuration files we ship, we use a different default for {{TCP.bind_addr}} and {{UDP.bind_addr}} than JGroups does.
> {code:xml}
> <TCP bind_addr="${jgroups.bind.address,jgroups.tcp.address:SITE_LOCAL}"/>
> <UDP bind_addr="${jgroups.bind.address,jgroups.udp.address:SITE_LOCAL}"/>
> {code}
> However, we didn't change the default for {{FD_SOCK}}, so it uses the JGroups default:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11847) Remove QueryBuilder and other deprecated dsl package usages
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11847?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11847:
-----------------------------------
Sprint: DataGrid Sprint #44, DataGrid Sprint #45 (was: DataGrid Sprint #44)
> Remove QueryBuilder and other deprecated dsl package usages
> -----------------------------------------------------------
>
> Key: ISPN-11847
> URL: https://issues.redhat.com/browse/ISPN-11847
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Affects Versions: 11.0.0.Dev05
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> The QueryBuilder and friends is deprecated, scheduled for removal in next major.
> We need to remove all its usages from tests and convert them to query string. There might be some tests that do not need to be converted because will be removed with the QueryBuilder when the time comes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11878) Embedded configuration builders should automatically be enabled when attributes configured
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11878?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11878:
-----------------------------------
Sprint: DataGrid Sprint #44, DataGrid Sprint #45 (was: DataGrid Sprint #44)
> Embedded configuration builders should automatically be enabled when attributes configured
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-11878
> URL: https://issues.redhat.com/browse/ISPN-11878
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Affects Versions: 11.0.0.Dev05
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> Currently it's neccessary for a user to do the following to configure the global state, as well serveral other configuration elements:
> {{globalBuilder.globalState().enable().persistentLocation(location)}}
> However the configuration of {{persistentLocation}} should be sufficient to enable the global state, i.e. the following should result in enabled(true) being called:
> {{globalBuilder.globalState().persistentLocation(location);}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (ISPN-11717) Deprecate ConsistentHashFactory customization
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11717?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11717:
-----------------------------------
Sprint: DataGrid Sprint #43, DataGrid Sprint #44, DataGrid Sprint #45 (was: DataGrid Sprint #43, DataGrid Sprint #44)
> 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
>
>
> 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)
5 years, 10 months