[ https://issues.apache.org/jira/browse/ATLAS-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161884#comment-17161884 ]
Damian Warszawski commented on ATLAS-3398: ------------------------------------------ According to our observations that can be a race condition between hive-hook (kafka event) and profiler (org.apache.atlas:atlas-client-v2:2.0.0). It can be also the case with atlas-client which make implicit retries while calling Atlas API. > Duplicates for unique attributes > --------------------------------- > > Key: ATLAS-3398 > URL: https://issues.apache.org/jira/browse/ATLAS-3398 > Project: Atlas > Issue Type: Bug > Components: atlas-core > Affects Versions: 2.0.0, trunk > Reporter: Bolke de Bruin > Priority: Blocker > Labels: integrity > Attachments: zrzut_ekranu_2019-09-03_o_10.28.50.png > > > We are seeing issues with entities being added to Atlas with duplicate > "qualifiedName". The guids differ and other attributes do also differ. Below > a graph that shows the distribution over time for duplicates. We have > difficulty determining which one is the right one (as they are different) in > order to clean them up. > We are also not the only ones encountering this as you can in the linked > issue. > We have noticed that Atlas does not use the > [locking|https://docs.janusgraph.org/master/advanced-topics/eventual-consistency/] > mechanism of Janus to prevent this: > > !zrzut_ekranu_2019-09-03_o_10.28.50.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)