You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2015/10/29 14:41:28 UTC
[jira] [Commented] (RANGER-706) Optimize audit db upgrade patches
to minimize timeout issues
[ https://issues.apache.org/jira/browse/RANGER-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980442#comment-14980442 ]
Gautam Borad commented on RANGER-706:
-------------------------------------
Committed to branch *ranger-0.5* : https://github.com/apache/incubator-ranger/commit/f47cbd13d9049462cf685748cf81be95c858da60
> Optimize audit db upgrade patches to minimize timeout issues
> ------------------------------------------------------------
>
> Key: RANGER-706
> URL: https://issues.apache.org/jira/browse/RANGER-706
> Project: Ranger
> Issue Type: Bug
> Components: admin, audit
> Affects Versions: 0.5.1
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 0.5.1
>
> Attachments: RANGER-706.patch
>
>
> Ranger upgrade times out while updating the DB schema from 0.4 to 0.5 (bunch of new tables, alter tables to add new columns, etc).
> This can happen, for example, while adding 3 columns to the audit table - as adding a column to an exiting table could be an expensive/time consuming task in MySQL (it involves: 1 - create temp table with new columns 2 - copy old table contents to new table 3 - drop the old table 4 - rename the new table to old table name). And patch script audit/015-auditlogaggregation.sql executes 3 ALTER TABLE statements, to add 3 columns to xa_access_audit table.
> This issue is likely to be hit in deployments that have large number of records in audit table. To be able to address this scenario, we should:
> - Optimize Audit db upgrade patches to minimize timeout issues
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)