Sharing Single Database

Master and failover installations of Iotellect Server may share the same non-clustered database. This database may be located:

  • On a separate physical machine
  • On the same physical machine with Master server or one of the failover servers

Pros and Cons

This method of configuring the database in the clustered environment is the simplest since it does not require any additional settings. However, in this case the database is not replicated and all data is stored in the single location. Thus, the database is a bottleneck of a whole failover cluster. Corruption of the data or failure of the database server software will cause service interruption. Therefore, such database setup has a few limited use cases.

Configuration

Below is the list of configuration changes required to set up Master and Failover nodes to use the single non-clustered database.

Database Server

  • Allow your database server to accept incoming connections from IP addresses of Master and all Failover nodes.
  • Allow firewall running on the database server host to accept connections on the database port (e.g. port 3306 for MySQL database) from IP addresses of Master and all Failover nodes.

Master Iotellect Server

  • If the server is already configured to connect to the above database server, leave its configuration intact.
  • Otherwise, switch your master server to the above database server.

Failover Iotellect Server

  • Use exactly the same database configuration as on the Master server.

If your database engine is running on the same physical machine with master server, you may need to change the database address in the Database URL setting from localhost to the IP address or host name of the Master server machine.

Was this page helpful?