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

[ElasticSearch] Remote cluster's IP (of ES endpoint) is mangled from localhost to wlan0's address

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Minor
    • None
    • 3.0
    • XDCR
    • Security Level: Public
    • None
    • Ubuntu 14.10-beta, 64 bit, CB-community-3.0.0, ElasticSearch 1.3.0, transport 2.0.0
    • Untriaged
    • Ubuntu 64-bit
    • Unknown

    Description

      Under Couchbase Console's XDCR tab, I set up a cluster reference to "127.0.0.1:9091" (or "localhost:9091") where my ElasticSearch is running. Then I set up a proper replication (using version 1).

      At this moment, the cluster reference's IP address or hostname gets rewritten to my development laptop's wlan0 IP address, e.g. "192.168.0.10:9091".

      The problem with this is that, depending on which network (e.g. work vs. home) I open the laptop, I get different IP address. That is, a previously set cluster reference becomes unusable, I have to destroy and create it again every time.

      Expected behavior: Whatever hostname or IP address I specify there should always remain the same, CB should not change it. If I say "localhost", it should stay "localhost".

      Attachments

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

        Activity

          People

            mschoch Marty Schoch [X] (Inactive)
            egmont Egmont Koblinger
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty