You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2015/06/02 01:39:18 UTC

[jira] [Commented] (AMBARI-11601) Point hbase.bulkload.staging.dir to accessible directory for unsecure deployment

    [ https://issues.apache.org/jira/browse/AMBARI-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568226#comment-14568226 ] 

Ted Yu commented on AMBARI-11601:
---------------------------------

Ran python tests under ambari-server which passed:
{code}
Ran 235 tests in 6.712s

OK
----------------------------------------------------------------------
Total run:747
Total errors:0
Total failures:0
OK
{code}

> Point hbase.bulkload.staging.dir to accessible directory for unsecure deployment
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-11601
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11601
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Ted Yu
>         Attachments: ambari-11601-v1.patch
>
>
> Since SecureBulkLoadEndpoint is loaded in unsecure hbase deployment, we need an accessible directory for hbase.bulkload.staging.dir
> By default, hbase.bulkload.staging.dir points to /user/$\{user.name\}/hbase-staging
> However, if /user/$\{user.name\} doesn't exist on hdfs, region server would abort when SecureBulkLoadEndpoint is started.
> This issue points hbase.bulkload.staging.dir to an accessible directory



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)