[jboss-jira] [JBoss JIRA] (WFLY-6210) Example ec2/gossip/azure server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)

Thursday, 25 February 2016

     [
https://issues.jboss.org/browse/WFLY-6210?page=com.atlassian.jira.plugin....
]

Radoslav Husar updated WFLY-6210:
---------------------------------
    Comment: was deleted

(was: Here is the diff after the fix:

{noformat}
[rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s
standalone/configuration/standalone-ha.xml docs/examples/configs/standalone-ec2-ha.xml
280,281c280,287
<                     <transport type="UDP"
socket-binding="jgroups-udp"/>
<                     <protocol type="PING"/>
---
...
                     <transport type="UDP"
socket-binding="jgroups-udp">
                         <property name="ip_mcast">false</property>
                     </transport>
                     <protocol type="S3_PING">
                         <property
name="access_key">${jboss.jgroups.s3_ping.access_key}</property>
                         <property
name="secret_access_key">${jboss.jgroups.s3_ping.secret_access_key}</property>
                         <property
name="location">${jboss.jgroups.s3_ping.bucket}</property>
                     </protocol> 284c290
<                     <protocol type="FD_ALL"/>
---
...
                     <protocol type="FD"/>
286c292,295
<                     <protocol type="pbcast.NAKACK2"/>
---
...
                     <protocol type="pbcast.NAKACK2">
                         <property
name="use_mcast_xmit">false</property>
                         <property
name="use_mcast_xmit_req">false</property>
                     </protocol> 291d299
<                     <protocol type="MFC"/>
296c304,308
<                     <protocol type="MPING"
socket-binding="jgroups-mping"/>
---
...
                     <protocol type="S3_PING">
                         <property
name="access_key">${jboss.jgroups.s3_ping.access_key}</property>
                         <property
name="secret_access_key">${jboss.jgroups.s3_ping.secret_access_key}</property>
                         <property
name="location">${jboss.jgroups.s3_ping.bucket}</property>
                     </protocol> 305d316
<                     <protocol type="MFC"/>
[rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s
standalone/configuration/standalone-ha.xml docs/examples/configs/standalone-azure-ha.xml
280,281c280,287
<                     <transport type="UDP"
socket-binding="jgroups-udp"/>
<                     <protocol type="PING"/>
---
...
                     <transport type="UDP"
socket-binding="jgroups-udp">
                         <property name="ip_mcast">false</property>
                     </transport>
                     <protocol type="azure.AZURE_PING">
                         <property
name="storage_account_name">${jboss.jgroups.azure_ping.storage_account_name}</property>
                         <property
name="storage_access_key">${jboss.jgroups.azure_ping.storage_access_key}</property>
                         <property
name="container">${jboss.jgroups.azure_ping.container}</property>
                     </protocol> 284c290
<                     <protocol type="FD_ALL"/>
---
...
                     <protocol type="FD"/>
286c292,295
<                     <protocol type="pbcast.NAKACK2"/>
---
...
                     <protocol type="pbcast.NAKACK2">
                         <property
name="use_mcast_xmit">false</property>
                         <property
name="use_mcast_xmit_req">false</property>
                     </protocol> 291d299
<                     <protocol type="MFC"/>
296c304,308
<                     <protocol type="MPING"
socket-binding="jgroups-mping"/>
---
...
                     <protocol
type="azure.AZURE_PING">
                         <property
name="storage_account_name">${jboss.jgroups.azure_ping.storage_account_name}</property>
                         <property
name="storage_access_key">${jboss.jgroups.azure_ping.storage_access_key}</property>
                         <property
name="container">${jboss.jgroups.azure_ping.container}</property>
                     </protocol> 305d316
<                     <protocol type="MFC"/>
[rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s
standalone/configuration/standalone-ha.xml docs/examples/configs/standalone-ec2-ha.xml
280,281c280,287
<                     <transport type="UDP"
socket-binding="jgroups-udp"/>
<                     <protocol type="PING"/>
---
...
                     <transport type="UDP"
socket-binding="jgroups-udp">
                         <property name="ip_mcast">false</property>
                     </transport>
                     <protocol type="S3_PING">
                         <property
name="access_key">${jboss.jgroups.s3_ping.access_key}</property>
                         <property
name="secret_access_key">${jboss.jgroups.s3_ping.secret_access_key}</property>
                         <property
name="location">${jboss.jgroups.s3_ping.bucket}</property>
                     </protocol> 284c290
<                     <protocol type="FD_ALL"/>
---
...
                     <protocol type="FD"/>
286c292,295
<                     <protocol type="pbcast.NAKACK2"/>
---
...
                     <protocol type="pbcast.NAKACK2">
                         <property
name="use_mcast_xmit">false</property>
                         <property
name="use_mcast_xmit_req">false</property>
                     </protocol> 291d299
<                     <protocol type="MFC"/>
296c304,308
<                     <protocol type="MPING"
socket-binding="jgroups-mping"/>
---
...
                     <protocol type="S3_PING">
                         <property
name="access_key">${jboss.jgroups.s3_ping.access_key}</property>
                         <property
name="secret_access_key">${jboss.jgroups.s3_ping.secret_access_key}</property>
                         <property
name="location">${jboss.jgroups.s3_ping.bucket}</property>
                     </protocol> 305d316
<                     <protocol type="MFC"/>
[rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s
standalone/configuration/standalone-ha.xml docs/examples/configs/standalone-gossip-ha.xml
280,281c280,286
<                     <transport type="UDP"
socket-binding="jgroups-udp"/>
<                     <protocol type="PING"/>
---
...
                     <transport type="UDP"
socket-binding="jgroups-udp">
                         <property name="ip_mcast">false</property>
                     </transport>
                     <protocol type="TCPGOSSIP">
                         <property
name="initial_hosts">${jboss.jgroups.gossip.initial_hosts}</property>
                         <property
name="num_initial_members">${jboss.jgroups.gossip.num_initial_members}</property>
                     </protocol> 284c289
<                     <protocol type="FD_ALL"/>
---
...
                     <protocol type="FD"/>
286c291,294
<                     <protocol type="pbcast.NAKACK2"/>
---
...
                     <protocol type="pbcast.NAKACK2">
                         <property
name="use_mcast_xmit">false</property>
                         <property
name="use_mcast_xmit_req">false</property>
                     </protocol> 291d298
<                     <protocol type="MFC"/>
296c303,306
<                     <protocol type="MPING"
socket-binding="jgroups-mping"/>
---
...
                     <protocol type="TCPGOSSIP">
                         <property
name="initial_hosts">${jboss.jgroups.gossip.initial_hosts}</property>
                         <property
name="num_initial_members">${jboss.jgroups.gossip.num_initial_members}</property>
                     </protocol> 305d314
<                     <protocol type="MFC"/>
{noformat})

...
 Example ec2/gossip/azure server profiles do not have any
modifications from the standard HA profiles (missing proper discovery protocols)

-----------------------------------------------------------------------------------------------------------------------------------------

                 Key: WFLY-6210
                 URL: https://issues.jboss.org/browse/WFLY-6210
             Project: WildFly
          Issue Type: Bug
          Components: Build System
    Affects Versions: 10.0.0.Final
            Reporter: Radoslav Husar
            Assignee: Radoslav Husar
            Priority: Critical
             Fix For: 10.1.0.Final

 {noformat}
 [rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s
standalone/configuration/standalone_xml_history/standalone-ha.initial.xml
docs/examples/configs/standalone-ec2-ha.xml
 Files standalone/configuration/standalone_xml_history/standalone-ha.initial.xml and
docs/examples/configs/standalone-ec2-ha.xml are identical
 {noformat}
 {noformat}
 [rhusar@syrah wildfly-10.1.0.Final-SNAPSHOT]$ diff -s
standalone/configuration/standalone_xml_history/standalone-ha.initial.xml
docs/examples/configs/standalone-gossip-ha.xml
 Files standalone/configuration/standalone_xml_history/standalone-ha.initial.xml and
docs/examples/configs/standalone-gossip-ha.xml are identical
 {noformat} 

--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[jboss-jira] [JBoss JIRA] (WFLY-6210) Example ec2/gossip/azure server profiles do not have any modifications from the standard HA profiles (missing proper discovery protocols)