[ https://issues.apache.org/jira/browse/OOZIE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
abhishek bafna updated OOZIE-2245: ---------------------------------- Fix Version/s: (was: trunk) 4.3.0 > Service to periodically check database schema > --------------------------------------------- > > Key: OOZIE-2245 > URL: https://issues.apache.org/jira/browse/OOZIE-2245 > Project: Oozie > Issue Type: New Feature > Components: core > Reporter: Robert Kanter > Assignee: Robert Kanter > Fix For: 4.3.0 > > Attachments: OOZIE-2245.002.patch, OOZIE-2245.003.patch, > OOZIE-2245.patch > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)