Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-10953

Support unicast addressing in cluster when well-known-addresses WKA are defined

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      It may be of interest to some of the customers to replace Multicast with "Well known Addresses" using Unicast.

      It could assist in bypassing known problems caused by using multicast and smart 'Cisco' switches, for example. Also some companies policy may not allow or support multicasting in their departments.

      [Cluster Troubleshooting page|
      http://confluence.atlassian.com/display/DOC/Cluster+Troubleshooting] suggests that some customers are using WKA instead of Multicast. The page in question:

      The Tangosol docs suggesting to place the specified changes in confluence_home/tangosol-coherence-override.xml

      <unicast-listener>
    <!--
    Note: Specifying one or more "well known" addresses (WKA) will disable
    all multicast communication. In this case, for a member to join the cluster
    it will either have to be a WKA or there will have to be at least one WKA
    member running.
    Note: The "localhost" setting may not work on systems that define
    localhost as the loopback address; in that case, specify the machine
    name or the specific IP address.
    -->
    <well-known-addresses>
      <socket-address id='1'>
        <address/>
        <port>8088</port>
      </socket-address>
    </well-known-addresses>
    <address>localhost</address>
    <port>8088</port>
    <port-auto-adjust>true</port-auto-adjust>
    <packet-buffer>
      <maximum-packets>1428</maximum-packets>
    </packet-buffer>
    <priority>8</priority>
  </unicast-listener>

          Form Name

            [CONFSERVER-10953] Support unicast addressing in cluster when well-known-addresses WKA are defined

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3579559 ] New: JAC Suggestion Workflow 3 [ 4337622 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3185646 ] New: JAC Suggestion Workflow 4 [ 3579559 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3036964 ] New: JAC Suggestion Workflow 2 [ 3185646 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2529794 ] New: JAC Suggestion Workflow [ 3036964 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2258297 ] New: Confluence Workflow - Public Facing v4 [ 2529794 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2194194 ] New: Confluence Workflow - Public Facing v3 [ 2258297 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1917910 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2194194 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1756372 ] New: Confluence Workflow - Public Facing v3 [ 1917910 ]
            jonah (Inactive) made changes -
            Description Original: It may be of interest to some of the customers to replace Multicast with {{"Well known Addresses"}} using Unicast.

            It could assist in bypassing known problems caused by using multicast and smart 'Cisco' switches, for example. Also some companies policy may not allow or support multicasting in their departments.

            [Cluster Troubleshooting page|
            http://confluence.atlassian.com/display/DOC/Cluster+Troubleshooting] suggests that some customers are using [WKA|http://wiki.tangosol.com/display/COH32UG/well-known-addresses] instead of Multicast. The page in question:

            The Tangosol docs suggesting to place the specified changes in confluence_home/tangosol-coherence-override.xml

            {code}
            <unicast-listener>
                <!--
                Note: Specifying one or more "well known" addresses (WKA) will disable
                all multicast communication. In this case, for a member to join the cluster
                it will either have to be a WKA or there will have to be at least one WKA
                member running.
                Note: The "localhost" setting may not work on systems that define
                localhost as the loopback address; in that case, specify the machine
                name or the specific IP address.
                -->
                <well-known-addresses>
                  <socket-address id='1'>
                    <address/>
                    <port>8088</port>
                  </socket-address>
                </well-known-addresses>
                <address>localhost</address>
                <port>8088</port>
                <port-auto-adjust>true</port-auto-adjust>
                <packet-buffer>
                  <maximum-packets>1428</maximum-packets>
                </packet-buffer>
                <priority>8</priority>
              </unicast-listener>
            {code}             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-10953].
              {panel}

            It may be of interest to some of the customers to replace Multicast with {{"Well known Addresses"}} using Unicast.

            It could assist in bypassing known problems caused by using multicast and smart 'Cisco' switches, for example. Also some companies policy may not allow or support multicasting in their departments.

            [Cluster Troubleshooting page|
            http://confluence.atlassian.com/display/DOC/Cluster+Troubleshooting] suggests that some customers are using [WKA|http://wiki.tangosol.com/display/COH32UG/well-known-addresses] instead of Multicast. The page in question:

            The Tangosol docs suggesting to place the specified changes in confluence_home/tangosol-coherence-override.xml

            {code}
            <unicast-listener>
                <!--
                Note: Specifying one or more "well known" addresses (WKA) will disable
                all multicast communication. In this case, for a member to join the cluster
                it will either have to be a WKA or there will have to be at least one WKA
                member running.
                Note: The "localhost" setting may not work on systems that define
                localhost as the loopback address; in that case, specify the machine
                name or the specific IP address.
                -->
                <well-known-addresses>
                  <socket-address id='1'>
                    <address/>
                    <port>8088</port>
                  </socket-address>
                </well-known-addresses>
                <address>localhost</address>
                <port>8088</port>
                <port-auto-adjust>true</port-auto-adjust>
                <packet-buffer>
                  <maximum-packets>1428</maximum-packets>
                </packet-buffer>
                <priority>8</priority>
              </unicast-listener>
            {code}
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-10953 [ CONFCLOUD-10953 ]

              Unassigned Unassigned
              ivan@atlassian.com Ivan Benko [Atlassian]
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: