atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-337) Hive import fails upon re-run if Atlas Server was restarted after abnormal termination
Date Fri, 27 Nov 2015 04:36:11 GMT

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

Hemanth Yamijala commented on ATLAS-337:
----------------------------------------

As per discussion with [~suma.shivaprasad], this will most likely go away due to optimization
changes being done for improving performance of Titan on HBase. Hence, this JIRA is mostly
to verify this issue once those are in.

> Hive import fails upon re-run if Atlas Server was restarted after abnormal termination
> --------------------------------------------------------------------------------------
>
>                 Key: ATLAS-337
>                 URL: https://issues.apache.org/jira/browse/ATLAS-337
>             Project: Atlas
>          Issue Type: Bug
>         Environment: Local
>            Reporter: Hemanth Yamijala
>
> Atlas trunk
> HBase is configured as backing store for Titan (Version 1.1.2).
> Steps to reproduce:
> * Start the Atlas server
> * Start hive import using import-hive.sh
> * While still in progress, terminate Atlas server with a kill -9
> * Restart Atlas server.
> * Restart Hive import process.
> Expectation is that the Hive import goes through fine. However, it failed with exceptions
indicating locks in HBase.



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

Mime
View raw message