We've seen a number of issues related to the database schema being incorrect (more than you would think). It seems some users go and muck around in the Oozie database, adding/removing columns and indexes, changing the default value of columns, etc. The issues caused by this can be very difficult to track down because their cause is not obvious and we generally assume the database schema is correct. For example, we saw an issue where Oozie was taking a long time to create Coordinator actions, and it turned out that the cause was that some indexes were missing, which made the Purge queries slow, which slowed down the whole database whenever the PurgeService ran. Another example was that the pause time was automatically being set whenever a Coordinator job was submitted, because the default value for the column was incorrect.
We should create a Service which periodically runs and checks that the schema is correct. It can output details about what's wrong to the log.
|Add support to the schema checker for SQLServer||Open||Unassigned|