hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <>
Subject [jira] [Commented] (HIVE-6602) Multi-user HiveServer2 throws error
Date Mon, 10 Mar 2014 14:47:43 GMT


Thejas M Nair commented on HIVE-6602:

This looks like a race condition between threads, where one thread has created the dir but
not set the permissions, and at that instance another thread finds that dir has been created
but later finds permissions are not what it expects.
Should we just synchronize this section of code ?
    if (!fs.exists(scratchDir)) {
      FsPermission fsPermission = new FsPermission((short)0777);
      fs.setPermission(scratchDir, fsPermission);

> Multi-user HiveServer2 throws error
> -----------------------------------
>                 Key: HIVE-6602
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 0.13.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>             Fix For: 0.13.0
>         Attachments: HIVE-6602.1.patch
> Error thrown:
> Error while processing statement: FAILED: RuntimeException
Permission denied: user=user_1, access=WRITE, inode="/tmp/hive-hive":hdfs:drwxr-xr-x
> For hive query execution, a scratch directory specified by hive.exec.scratchdir is created
with default permission 700. In HiveServer2, during the CLIService startup, we check for the
presence of scratch directories (local + dfs) and if they don't exist, create them with permission
777. However, we should also change the permission from the default 700 to 777 in case the
dfs scratch directory already exists.

This message was sent by Atlassian JIRA

View raw message