View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004024||SymmetricDS||Improvement||public||2019-06-20 15:15||2019-06-20 15:15|
|Target Version||3.11.0||Fixed in Version|
|Summary||0004024: When instance comes up, if in cluster mode and auto.config.database is true, should get lock before updating database|
|Description||More than one node in a SymmetricDS cluster should not attempt to configure the database at the same time.|
Many times there are longer running steps to modify the database (e.g., primary key change requires moving data to a temporary table, drop the original table, recreate the modified table, and move the data to the new table).
If SymmetricDS is running in a cluster (cluster.lock.enabled=true) and automatic configuration of the database is set to true (auto.config.database=true), then before executing the check of the DDL changes and the execution of the DDL changes, the node should retrieve a cluster lock. It should not continue on until it successfully gets a cluster lock.
The first one in the cluster that gets the lock will execute any DDL changes necessary, and all others that follow will check and see no changes to execute.
|Tags||No tags attached.|