[FALCON-708] Falcon assumes a default umask in HDFS for staging dir

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.5, 0.6
• Fix Version/s: 0.6
• Component/s: oozie
• Assignee: Venkatesh Seetharam
• Reporter: Venkatesh Seetharam
• Created: 11/Sep/14 02:14
• Updated: 07/Nov/14 19:43
• Resolved: 07/Nov/14 19:43

Description

Falcon needs to have 750 on staging so oozie can read workflow definitions. If the default umask is changed, falcon becomes unusable and workflows cannot be scheduled.

Issue Links

• is related to: FALCON-816 Fallback to Falcon FileSystem (logged in user) when ACL is not available in LogCleanupService
• relates to: FALCON-673 feed schedule trying to create staging path as ACL owner

Sub-Tasks

• Override the permissions for staging and working dirs with 755: Resolved
• Change the ownership for staging dir to user submitting the feed: Resolved
• Falcon Dashboard unusable when server is started with umask 077: Resolved