[ https://issues.apache.org/jira/browse/ATLAS-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986051#comment-16986051 ]
Bolke de Bruin edited comment on ATLAS-3305 at 12/2/19 1:34 PM: ---------------------------------------------------------------- I suggest using a different topic for this (ATLAS_PARTIONED) or having a different config item (token.partioned) to ensure administrators know what to do with this (making sure that the messages are atomic and/or partioned by key). was (Author: bolke): I suggest using a different topic for this (ATLAS_PARTIONED) to ensure administrators know what to do with this (making sure that the messages are atomic and/or partioned by key). > Unable to scale atlas kafka consumers > ------------------------------------- > > Key: ATLAS-3305 > URL: https://issues.apache.org/jira/browse/ATLAS-3305 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-intg > Affects Versions: 1.1.0, 2.0.0 > Reporter: Adam Rempter > Priority: Major > Labels: performance > Attachments: ATLAS-3305_multiple_kafka_consumers.patch, > multiple_consumers_perf.png > > Time Spent: 10m > Remaining Estimate: 0h > > We wanted to scale kafka consumers for atlas, as we are getting many lineage > messages and processing them just with one consumer is not enough. > > There is parameter atlas.notification.hook.numthreads to scale consumers in > NotificationHookConsumer. > But the method: > > notificationInterface.createConsumers(NotificationType.HOOK, numThreads) > > is always returning one element list, which effectively always starts one > consumer > List<NotificationConsumer<T>> consumers = > Collections.singletonList(kafkaConsumer); > > Log incorrectly says that nuber of consumers has been created: > LOG.info("<== KafkaNotification.createConsumers(notificationType={}, > numConsumers={}, autoCommitEnabled={})", notificationType, numConsumers, > autoCommitEnabled) -- This message was sent by Atlassian Jira (v8.3.4#803005)