carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravindra Pesala (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CARBONDATA-174) When hadoop.tmp.dir configured incorrectly, hdfs lock of carbon would throw exception.
Date Sat, 24 Sep 2016 10:45:20 GMT

     [ https://issues.apache.org/jira/browse/CARBONDATA-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ravindra Pesala updated CARBONDATA-174:
---------------------------------------
    Fix Version/s: 0.1.1-incubating
                   0.2.0-incubating

> When hadoop.tmp.dir configured incorrectly, hdfs lock of carbon would throw exception.
> --------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-174
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-174
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: zhangshunyu
>            Assignee: zhangshunyu
>             Fix For: 0.2.0-incubating, 0.1.1-incubating
>
>
> 1. The hdfs lock file for one table should be put inside this table's store path, this
is more reasonable, and if the store path is not set, then we put it into hadoop.tmp.dir.
For example: if the store path of carbon on hdfs is /user/hive/warehouse/carbon.store, then
the lock file for this table woud be: /user/hive/warehouse/carbon.store/default/table_name/meta.lock
> 2. This bug is found by : Some times, hadoop configured wrong hadoop.tmp.dir, hadoop
can still work normally, but carbon's hdfs lock can not work normally, it will throws exception:
"Table is locked for updation. Please try after some time".



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

Mime
View raw message