[jboss-jira] [JBoss JIRA] (WFLY-9877) NAKACK, UNICAST2 and MERGE2 need to translate to their newer variants

[Richard Janík (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Janík updated WFLY-9877:
--------------------------------
    Description: 
This is only an issue for EAP, which has different versions than WFLY, for that reason, all the versions mentioned here are EAP ones.

After some discussion with people who test migrations, we found that these protocols that were deprecated in JGroups 3.6.x present in 7.1.0 and were removed in JGroups 4.0.10 present in 7.2.0 should be brought back in some form:
{noformat}
NAKACK --> NAKACK2
UNICAST2 --> UNICAST3
MERGE2 --> MERGE3
{noformat}

These are not in the default 7.0 or 7.1 configuration, so why do we need to translate these like we do it for NAKACK2? Because these protocols can be expected to be present in the 7.1 configuration due to migration from 6.x, where they are by default. Since, after migration from 6.x, these will work with the 7.1 configuration, and since there is a reason to expect them being used even if they are deprecated, we should not just silently remove these protocols with the JGroups upgrade that is in 7.2 - the configuration file from 7.1 should always work with 7.2.

Cc [~msvehla] [~pkremens]

  was:
This is only an issue for EAP, which has different versions than WFLY, for that reason, all the versions mentioned here are EAP ones.

After some discussion with people who test migrations, we found out that these protocols need to be translated to:
{noformat}
NAKACK --> NAKACK3
NAKACK2 --> NAKACK3 (already done)
UNICAST2 --> UNICAST3
MERGE2 --> MERGE3
{noformat}

These are not in the default 7.0 or 7.1 configuration, so why do we need to translate these like we do it for NAKACK2? Because these protocols can be expected to be present in the 7.1 configuration due to migration from 6.x, where they are by default. Since, after migration from 6.x, these will work with the 7.1 configuration, and since there is a reason to expect them being used even if they are deprecated, we should not just silently remove these protocols with the JGroups upgrade that is in 7.2 - the configuration file from 7.1 should always work with 7.2.

Cc [~msvehla] [~pkremens]



> NAKACK, UNICAST2 and MERGE2 need to translate to their newer variants
> ---------------------------------------------------------------------
>
>                 Key: WFLY-9877
>                 URL: https://issues.jboss.org/browse/WFLY-9877
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 12.0.0.Beta1
>            Reporter: Richard Janík
>            Assignee: Paul Ferraro
>
> This is only an issue for EAP, which has different versions than WFLY, for that reason, all the versions mentioned here are EAP ones.
> After some discussion with people who test migrations, we found that these protocols that were deprecated in JGroups 3.6.x present in 7.1.0 and were removed in JGroups 4.0.10 present in 7.2.0 should be brought back in some form:
> {noformat}
> NAKACK --> NAKACK2
> UNICAST2 --> UNICAST3
> MERGE2 --> MERGE3
> {noformat}
> These are not in the default 7.0 or 7.1 configuration, so why do we need to translate these like we do it for NAKACK2? Because these protocols can be expected to be present in the 7.1 configuration due to migration from 6.x, where they are by default. Since, after migration from 6.x, these will work with the 7.1 configuration, and since there is a reason to expect them being used even if they are deprecated, we should not just silently remove these protocols with the JGroups upgrade that is in 7.2 - the configuration file from 7.1 should always work with 7.2.
> Cc [~msvehla] [~pkremens]



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)