Configure Locators for WAN Member Discovery

When you start a SQLFire locator in a WAN deployment, you must specify additional configuration options to identify each SQLFire cluster in the WAN.

Important Configuration Notes


Procedure


  1. Start a locator for a SQLFire cluster. For example, to start a locator for SQLFire cluster 1 shown in Figure 2:
    sqlf locator start
         -peer-discovery-address=ds1host
         -peer-discovery-port=10101
         -locators=ds1host:10101
         -conserve-sockets=false
         -distributed-system-id=1
         -remote-locators=ds2host[20202],ds3host[30303]

    The above command configures the local SQLFire distributed system (with -distributed-system-id=1) to replicate to two different remote SQLFire distributed systems using standalone locators.

    Note: -peer-discovery-address and -peer-discovery-port identify the network connection that local SQLFire members use to discovery each other in the distributed system. -locators identifies all of the locators used in the distributed system (the above example uses the single, standalone locator that the sqlf command starts). These parameters are always used when starting locators, regardless of whether WAN replication is configured. See Using Locators for more information.
  2. To start a locator in SQLFire cluster 2, you would enter a command similar to:
    sqlf locator start
         -peer-discovery-address=ds2host
         -peer-discovery-port=20202
         -locators=ds2host:20202
         -conserve-sockets=false
         -distributed-system-id=2
         -remote-locators=ds1host[10101],ds2host[20203]

    The preceding commands ensure that both cluster 1 and cluster 2 are associated with one another (and to cluster 3), and can replicate or receive data as necessary.