[
https://issues.apache.org/jira/browse/FALCON-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balu Vellanki updated FALCON-1648:
----------------------------------
Description:
Today, when specifying a cluster entity, user should create three dirs in HDFS
with proper permissions.
1. staging
2. tmp
3. working
We can simplify this by letting user specify a single location, i.e. staging.
The working dir will be created by falcon under <staging_dir>/working. The tmp
dir will be <staging_dir>/tmp. User can still overwrite these values in the
cluster.xml, this way the cluster definition is backwards compatible.
Falcon-817 was supposed to address this issue. But when I submit a cluster
entity without working and temp locations, the submission fails with following
error.
{code}
2015-12-03 00:13:19,759 ERROR - [1209485672@qtp-681008168-1778 -
adfa8c22-a42e-4555-ad98-52e9d14bc97f:ambari-qa:POST//entities/submit/cluster] ~
Unable to persist entity object (AbstractEntityManager:203)
org.apache.falcon.FalconException: Failed to copy shared libs to
clusterprimaryCluster2
at
org.apache.falcon.service.SharedLibraryHostingService.addLibsTo(SharedLibraryHostingService.java:107)
...
Caused by: org.apache.hadoop.security.AccessControlException: Permission
denied: user=falcon, access=WRITE,
inode="/apps/falcon/primaryCluster/staging2/working/lib":ambari-qa:hdfs:drwxr-xr-x
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
{code}
was:
Today, when specifying a cluster entity, user should create three dirs in HDFS
with proper permissions.
1. staging
2. tmp
3. working
We can simplify this by letting user specify a single location, i.e. staging.
The working dir will be created by falcon under <staging_dir>/working. The tmp
dir will be <staging_dir>/tmp. User can still overwrite these values in the
cluster.xml, this way the cluster definition is backwards compatible.
> Usability : Require user to provide only the staging location.
> ---------------------------------------------------------------
>
> Key: FALCON-1648
> URL: https://issues.apache.org/jira/browse/FALCON-1648
> Project: Falcon
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Balu Vellanki
> Assignee: Balu Vellanki
> Fix For: 0.9
>
>
> Today, when specifying a cluster entity, user should create three dirs in
> HDFS with proper permissions.
> 1. staging
> 2. tmp
> 3. working
> We can simplify this by letting user specify a single location, i.e. staging.
> The working dir will be created by falcon under <staging_dir>/working. The
> tmp dir will be <staging_dir>/tmp. User can still overwrite these values in
> the cluster.xml, this way the cluster definition is backwards compatible.
> Falcon-817 was supposed to address this issue. But when I submit a cluster
> entity without working and temp locations, the submission fails with
> following error.
> {code}
> 2015-12-03 00:13:19,759 ERROR - [1209485672@qtp-681008168-1778 -
> adfa8c22-a42e-4555-ad98-52e9d14bc97f:ambari-qa:POST//entities/submit/cluster]
> ~ Unable to persist entity object (AbstractEntityManager:203)
> org.apache.falcon.FalconException: Failed to copy shared libs to
> clusterprimaryCluster2
> at
> org.apache.falcon.service.SharedLibraryHostingService.addLibsTo(SharedLibraryHostingService.java:107)
> ...
> Caused by: org.apache.hadoop.security.AccessControlException: Permission
> denied: user=falcon, access=WRITE,
> inode="/apps/falcon/primaryCluster/staging2/working/lib":ambari-qa:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
