Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-11

Starting Confluence DC as a docker or ECS in AWS environment with clustering mode set to AWS will fail.

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • None
    • 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.

    Description

      Issue Summary

      Starting Confluence DC as Docker or ECS in AWS environment with clustering mode set to AWS will fail with error unable to find EC2 instance.

      Steps to Reproduce

      1. Create an EC2 instance in AWS.
      2. Follow the Confluence Docker Datacenter documentation to run confluence.
      3. During the configuration phase use the AWS as a "ATL_CLUSTER_TYPE".

      Expected Results

      The instance will start without any problems.

      Actual Results

      The instance will start with an incorrect cluster and with the error.
      Starting another node will cause cluster panic as nodes can not talk to each other
      (cluster failed).

      The below exception is thrown in the Atlassian-confluence.log file:

      Datacenter AWS hazelcast ... No EC2 instances found!
      

      Workaround

      Use TCP_ip clusterin mode, or use the Cloud formation template if you need to dynamically add instances.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              gpaunovic g
              Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: