[RANGER-1173] Improve Ranger database schema import logic and make it more robust

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0, 0.6.0, 0.7.0, 0.6.1
• Fix Version/s: 0.7.0, 0.6.2
• Component/s: Ranger
• Assignee: Pradeep Agrawal
• Reporter: Pradeep Agrawal
• Created: 12/Sep/16 13:29
• Updated: 13/Sep/16 14:42
• Resolved: 13/Sep/16 14:42

Description

Problem Statement: Ranger installation process should handle concurrent import of DB schema as concurrent execution of db schema files can lead to an inconsistent state of data and application.

Proposed Solution : Before importing db schema file; installation process will insert status in x_db_version_h table with active='N' value. If schema will get created/imported successfully then status of the schema creation flag will be set to 'Y' else status row from x_db_version_h will be deleted. If the Ranger DB schema is being imported then the active column will have the value 'N' and no other process will be allowed to import that file.

Issue Links

• is related to: RANGER-910 Improve db and java patches execution logic to make that more robust
• links to: Apache review request link-1