You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2015/10/09 03:29:27 UTC

[jira] [Created] (ATLAS-215) Configure Consumer Groups for Notifications

Tom Beerbower created ATLAS-215:
-----------------------------------

             Summary: Configure Consumer Groups for Notifications
                 Key: ATLAS-215
                 URL: https://issues.apache.org/jira/browse/ATLAS-215
             Project: Atlas
          Issue Type: Bug
            Reporter: Tom Beerbower
            Assignee: Tom Beerbower


Currently with the notification framework we set the properties so that all consumers are created in a single group...

{code}
        //todo take group id as argument to allow multiple consumers??
        properties.put(ConsumerConfig.GROUP_ID_CONFIG, ATLAS_GROUP);
{code}

Having Kafka consumers for both the HOOK and ENTITIES topics in a single group causes this issue ...

{code}
java.lang.IllegalArgumentException: requirement failed: Round-robin assignment is allowed only if all consumers in the group subscribe to the same topics, AND if the stream counts across topics are identical for a given consumer instance.
Topic ATLAS_ENTITIES has the following available consumer streams: Set(atlas_c6401.ambari.apache.org-1443714948705-e518b690-0)
Topic ATLAS_HOOK has the following available consumer streams: Set(atlas_c6401.ambari.apache.org-1443714214755-8fd9a5f8-0)
{code}

We shouldn't have HOOK consumers and ENTITIES consumers in the same group.  





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