You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@carbondata.apache.org by "zhangshunyu (JIRA)" <ji...@apache.org> on 2016/08/24 06:52:22 UTC

[jira] [Created] (CARBONDATA-174) When hadoop.tmp.dir configured incorrectly, hdfs lock of carbon would throw exception.

zhangshunyu created CARBONDATA-174:
--------------------------------------

             Summary: 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


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)