Provide more information why DATABASECHANGELOGLOCK was inserted
Can we please get additional information inserted when DATABASECHANGELOGLOCK is put in the DB.
For example ;
-Process that inserted the row (start-up/upgrade)
-Where it came from (local/node2)
-Timestamp of insertion
Right now, when Yellowfin starts up, or runs an upgrade, the DATABASECHANGELOGLOCK row is inserted to ensure there dupe processes are not trying to update the DB. This will then be removed post start-up or upgrade. This is good.
However.. in cases of failed startups and upgrades, that DATABASECHANGELOGLOCK row will not remove. Yes there are underlying reasons for this, but it's near impossible to identify if that record was inserted due to a bad node 3 months ago.