SQLite using DB file across RHEL VIrtual Machines

[Rob Lindsey]

For a new prod environment I am trying to setup a SQLite DB file that each instance of CL would be able to read from and/or write to. There may be as many as 5 VMs that would need to read this DB file. I don’t want to have one VM to be the main system that hosts the Db file. The reason why is because that is a point of failure if that VM goes down, I don’t want the other CL VMs to have to wait or fail because they cannot read the DB.

Has anyone designed and built something like this?  I am using the SQLite DB as my routing table, I know not the usual way to do this but with upward of 60,000 entries I don’t want to have that many entries in the routing tab or in a CL table.  Yes each system will need to operate as independent system but there might be a need to send data across systems.

Hope the above makes sense.

TIA

Rob

Topic

[Rob Abbott]

Be careful with the locking scheme you choose.  

There is a write locking scheme that only works on the local machine – this is what we use for SMAT DB for performance reasons.

I think there are others that are not as fast but work on shared media across servers.

I believe you choose the locking scheme when you create the database.

Otherwise it should work fine.

Rob Abbott
Cloverleaf Emeritus

[Author]

Replies