Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-23580

Docs for Configuring AZURE_PING are incorrect

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 7.4.0.GA
    • Documentation
    • None
    • False
    • None
    • False

    Description

      Pertaining to the documentation located at:

      https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.4/html-single/using_jboss_eap_in_microsoft_azure/index#using_jboss_eap_high_availability_in_microsoft_azure

      > By default, JGroups uses the UDP stack. If you were using another stack, change back to using the UDP stack:
      > [standalone@embedded /] /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=udp)

      We should recommend using TCP stack instead, e.g.:

      > By default, JGroups uses the UDP stack. If you were using another stack, change it to use the TCP stack:
      > [standalone@embedded /] /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)

      e.g. https://github.com/Azure/rhel-jboss-templates/blob/master/eap74-rhel8-payg-multivm/src/main/scripts/jbosseap-setup-redhat.sh#L133 already does this

      > Execute the following batch of commands to remove the existing UDP stack and insert a new UDP stack configured for Microsoft Azure:

      The provided script uses out of date protocol stack. The resulting one should look like this one:

                      <stack name="tcp">
                          <transport type="TCP" socket-binding="jgroups-tcp"/>
                          <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>
                          <protocol type="MERGE3"/>
                          <socket-protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
                          <protocol type="FD_ALL"/>
                          <protocol type="VERIFY_SUSPECT"/>
                          <protocol type="pbcast.NAKACK2"/>
                          <protocol type="UNICAST3"/>
                          <protocol type="pbcast.STABLE"/>
                          <protocol type="pbcast.GMS"/>
                          <protocol type="FRAG3"/>
                      </stack>
      

      i.e. replace FD_ALL with FD; remove UFC, replace FRAG2 with FRAG3

      As of assigning the issue to the docs team, we are still investigating why the existing UDP configuration doesn't appear to work, so we might be updating the issue further.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rhn-engineering-rhusar Radoslav Husar
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: