Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-57329

XDCR: Peering issue in AWS due to blackhole entries in routing tables

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • Morpheus
    • 7.1.3
    • XDCR
    • None
    • Untriaged
    • 0
    • Unknown

    Description

      As observed in CBSE-14091, the replication creation was failing due to lack of connectivity between two AWS Capella clusters. This is due to 'blackhole' entries in the VPC peering tables:

      "RouteTableId": "rtb-0a05dd56a23efb56a",            "Routes": [                {                    "DestinationCidrBlock": "10.12.66.0/23",                    "GatewayId": "local",                    "Origin": "CreateRouteTable",                    "State": "active"                },                {                    "DestinationCidrBlock": "10.12.68.0/23",                    "Origin": "CreateRoute",                    "State": "blackhole",                    "VpcPeeringConnectionId": "pcx-0e6255bf69eb02f1d"                },                {                    "DestinationCidrBlock": "0.0.0.0/0",                    "GatewayId": "igw-0db7ee7362a4929f4",                    "Origin": "CreateRoute",                    "State": "active"                }            ],

      The blackhole state means that the target is not reachable (ref: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_Route.html)

       

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            sudeep.jathar Sudeep Jathar
            sudeep.jathar Sudeep Jathar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty