Multiple SymmetricDS instances at same host

I’m looking at running multiple SymmetricDS instances to do replication between different environments independently, e.g. Oracle Test -> Postgres Test, Oracle Dev -> Postgres Dev. The instances will run in Docker containers in a Mesos cluster, possibly at the same host. I see that SymmetricDS store the sync.url in the SYM_NODE table. Since I’ve up to now only have had one SymmetricDS instance, the port is hard coded in the engine/*.properties files:


Could this potentially cause problems, since the sync.url will be identical for both instances?

  • `docker attach` command can't enter into a container unless Ctrl+C or Enter pressed
  • Docker VOLUME for different users
  • Publish docker container port and access that port from another docker container
  • Docker with Nginx - Https not working
  • Docker pushing containers to private registry
  • Docker registry and index
  • Docker: How to connect to Postgresql container without exposing port
  • “CMD ['/home/user/']” in docker file doesn't work with docker-compose
  • Error run scrapy after install docker
  • List folders in Docker Elastic Beanstalk instance
  • Run a Docker image as a command line utility in Windows?
  • line 113: conf/neo4j.conf: Permission denied
  • 2 Solutions collect form web for “Multiple SymmetricDS instances at same host”

    You can run multiple SymmetricDS nodes in the same instance. It is called multi-homing. All you do is simply add multiple .properties files under the engines directory. You distinguish between the two nodes using different parameters which show up in the sync.url.

    The sync.url is:

    http://{symmetricds installation host name or dns name}:{symmetricds port configured in}/sync/{}

    If you don’t need to reach the SymmetricDS process from outside the Docker container, both instances can use the same port(s). Just make sure to run the Docker container in Bridge mode (not Host), and don’t expose any ports.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.