[
https://issues.apache.org/jira/browse/ATLAS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298263#comment-15298263
]
Hemanth Yamijala commented on ATLAS-503:
----------------------------------------
I am able to replicate the issue with a test case that tries to create multiple
tags at the same time. The exception stack trace shows a
{{PermanentLockingException}}. This is being thrown from the shaded
{{atlas-titan}} module and specifically the
{{HBaseKeyColumnValueStore.acquireLock}} method.
Turning on some debug statements, it looks like many threads are trying to
acquire a transactional lock from these objects, and for some reason, they are
all trying to acquire a lock on the same key, column, even though the tags
being created are different. Further, we don't have any retries in place to
handle a failure to acquire a lock, with the result that we are immediately
failing in such situations.
So, two questions to consider:
* What are these keys / columns on which everyone is trying to acquire a lock?
* If this is a valid scenario and there is this much contention, should we
possibly add some retries until the lock succeeds?
Doing further debugging on these lines.
> Not all Hive tables are not imported into Atlas when interrupted with search
> queries while importing.
> -------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-503
> URL: https://issues.apache.org/jira/browse/ATLAS-503
> Project: Atlas
> Issue Type: Bug
> Reporter: Sharmadha Sainath
> Assignee: Hemanth Yamijala
> Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: hiv2atlaslogs.rtf
>
>
> On running a file containing 100 table creation commands using beeline -f ,
> all hive tables are created. But only 81 of them are imported into Atlas
> (HiveHook enabled) when queries like "hive_table" is searched frequently
> while the import process for the table is going on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
