Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-10953

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



    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? 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

          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.
            <socket-address id='1'>


        Issue Links



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