[jira] [Commented] (ATLAS-3874) NotificationHookConsumer: Shell Entity Resolution When Multiple Consumers Process Same Entity
[ https://issues.apache.org/jira/browse/ATLAS-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17189024#comment-17189024 ] ASF subversion and git services commented on ATLAS-3874: Commit 3468c2b4ac1175849ce119dcd69f5518b1d9a342 in atlas's branch refs/heads/master from Ashutosh Mestry [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3468c2b ] ATLAS-3874: NotificationHookConsumer: Concurrent Message Processing Change-Id: Ia5ccc6aeea2b0c44493636243b7627d16ad32c8f Signed-off-by: Sarath Subramanian > NotificationHookConsumer: Shell Entity Resolution When Multiple Consumers > Process Same Entity > - > > Key: ATLAS-3874 > URL: https://issues.apache.org/jira/browse/ATLAS-3874 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0, trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > > *Background* > Atlas has ability to consume messages from multiple hooks. When doing so, if > there are messages in multiple queue requesting creation of the same entity, > then this case leads to a race condition. > *Steps to Duplicate* > _Pre-requisites_ > Atlas should be configured to consume from 2 Kafka queues viz. _queue1_ and > _queue2_. > _Steps:_ > # Add a message in _queue1_ that references a non-existent entity. > # Add a message in _queue2_ that creates the entity in step 1. > _Expected behavior_: > Shell entity should get created in step 1 that is resolved into first class > entity in step 2. > _Actual behavior:_ > Shell entity is not resolved. A duplicate entity with same _qualifiedName_ > gets created. > *Root Cause* > The _NotificationHookConsumer_ is not aware of messages processed by other > consumers there by leading to concurrent entity creation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3874) NotificationHookConsumer: Shell Entity Resolution When Multiple Consumers Process Same Entity
[ https://issues.apache.org/jira/browse/ATLAS-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17189026#comment-17189026 ] ASF subversion and git services commented on ATLAS-3874: Commit dae104355697ae1280fe7dc6b0d9a685a53caee3 in atlas's branch refs/heads/branch-2.0 from Ashutosh Mestry [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=dae1043 ] ATLAS-3874: NotificationHookConsumer: Concurrent Message Processing Change-Id: Ia5ccc6aeea2b0c44493636243b7627d16ad32c8f Signed-off-by: Sarath Subramanian (cherry picked from commit 3468c2b4ac1175849ce119dcd69f5518b1d9a342) > NotificationHookConsumer: Shell Entity Resolution When Multiple Consumers > Process Same Entity > - > > Key: ATLAS-3874 > URL: https://issues.apache.org/jira/browse/ATLAS-3874 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0, trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > > *Background* > Atlas has ability to consume messages from multiple hooks. When doing so, if > there are messages in multiple queue requesting creation of the same entity, > then this case leads to a race condition. > *Steps to Duplicate* > _Pre-requisites_ > Atlas should be configured to consume from 2 Kafka queues viz. _queue1_ and > _queue2_. > _Steps:_ > # Add a message in _queue1_ that references a non-existent entity. > # Add a message in _queue2_ that creates the entity in step 1. > _Expected behavior_: > Shell entity should get created in step 1 that is resolved into first class > entity in step 2. > _Actual behavior:_ > Shell entity is not resolved. A duplicate entity with same _qualifiedName_ > gets created. > *Root Cause* > The _NotificationHookConsumer_ is not aware of messages processed by other > consumers there by leading to concurrent entity creation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
