[jira] [Updated] (KAFKA-2901) Extend ListGroups and DescribeGroup APIs to cover offsets
[ https://issues.apache.org/jira/browse/KAFKA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2901: --- Fix Version/s: (was: 0.10.1.0) > Extend ListGroups and DescribeGroup APIs to cover offsets > - > > Key: KAFKA-2901 > URL: https://issues.apache.org/jira/browse/KAFKA-2901 > Project: Kafka > Issue Type: Improvement > Components: consumer >Affects Versions: 0.9.0.0 >Reporter: Andy Coates >Assignee: Jason Gustafson > > The {{ListGroupsRequest}} and {{DescribeGroupsRequest}} added to 0.9.0.0 > allow admin tools to get details of consumer groups now that this information > is not stored in ZK. > The brokers also now store offset information for consumer groups. At > present, there is no API for admin tools to discover the groups that brokers > are storing offsets for. > For example, if a consumer is using the new consumer api, is storing offsets > in Kafka under the groupId 'Bob', but is using manual partition assignment, > then the {{groupCache}} in the {{GroupMetadataManager}} will not contain any > information about the group 'Bob'. However, the {{offsetCache}} in the > {{GroupMetadataManager}} will contain information about 'Bob'. > Currently the only way for admin tools to know the full set of groups being > managed by Kafka, i.e. those storing offsets in Kafka, those using Kafka for > balancing of consumer groups, and those using Kafka for both, is to consume > the offset topic. > We need to extend the List/Describe groups API to allow admin tools to > discover 'Bob' and allow the partition offsets to be retrieved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2901) Extend ListGroups and DescribeGroup APIs to cover offsets
[ https://issues.apache.org/jira/browse/KAFKA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2901: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Extend ListGroups and DescribeGroup APIs to cover offsets > - > > Key: KAFKA-2901 > URL: https://issues.apache.org/jira/browse/KAFKA-2901 > Project: Kafka > Issue Type: Improvement > Components: consumer >Affects Versions: 0.9.0.0 >Reporter: The Data Lorax >Assignee: Neha Narkhede > Fix For: 0.10.1.0 > > > The {{ListGroupsRequest}} and {{DescribeGroupsRequest}} added to 0.9.0.0 > allow admin tools to get details of consumer groups now that this information > is not stored in ZK. > The brokers also now store offset information for consumer groups. At > present, there is no API for admin tools to discover the groups that brokers > are storing offsets for. > For example, if a consumer is using the new consumer api, is storing offsets > in Kafka under the groupId 'Bob', but is using manual partition assignment, > then the {{groupCache}} in the {{GroupMetadataManager}} will not contain any > information about the group 'Bob'. However, the {{offsetCache}} in the > {{GroupMetadataManager}} will contain information about 'Bob'. > Currently the only way for admin tools to know the full set of groups being > managed by Kafka, i.e. those storing offsets in Kafka, those using Kafka for > balancing of consumer groups, and those using Kafka for both, is to consume > the offset topic. > We need to extend the List/Describe groups API to allow admin tools to > discover 'Bob' and allow the partition offsets to be retrieved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2901) Extend ListGroups and DescribeGroup APIs to cover offsets
[ https://issues.apache.org/jira/browse/KAFKA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2901: --- Fix Version/s: (was: 0.9.0.1) 0.9.1.0 > Extend ListGroups and DescribeGroup APIs to cover offsets > - > > Key: KAFKA-2901 > URL: https://issues.apache.org/jira/browse/KAFKA-2901 > Project: Kafka > Issue Type: Improvement > Components: consumer >Affects Versions: 0.9.0.0 >Reporter: The Data Lorax >Assignee: Neha Narkhede > Fix For: 0.9.1.0 > > > The {{ListGroupsRequest}} and {{DescribeGroupsRequest}} added to 0.9.0.0 > allow admin tools to get details of consumer groups now that this information > is not stored in ZK. > The brokers also now store offset information for consumer groups. At > present, there is no API for admin tools to discover the groups that brokers > are storing offsets for. > For example, if a consumer is using the new consumer api, is storing offsets > in Kafka under the groupId 'Bob', but is using manual partition assignment, > then the {{groupCache}} in the {{GroupMetadataManager}} will not contain any > information about the group 'Bob'. However, the {{offsetCache}} in the > {{GroupMetadataManager}} will contain information about 'Bob'. > Currently the only way for admin tools to know the full set of groups being > managed by Kafka, i.e. those storing offsets in Kafka, those using Kafka for > balancing of consumer groups, and those using Kafka for both, is to consume > the offset topic. > We need to extend the List/Describe groups API to allow admin tools to > discover 'Bob' and allow the partition offsets to be retrieved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-2901) Extend ListGroups and DescribeGroup APIs to cover offsets
[ https://issues.apache.org/jira/browse/KAFKA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] The Data Lorax updated KAFKA-2901: -- Description: The {{ListGroupsRequest}} and {{DescribeGroupsRequest}} added to 0.9.0.0 allow admin tools to get details of consumer groups now that this information is not stored in ZK. The brokers also now store offset information for consumer groups. At present, there is no API for admin tools to discover the groups that brokers are storing offsets for. For example, if a consumer is using the new consumer api, is storing offsets in Kafka under the groupId 'Bob', but is using manual partition assignment, then the {{groupCache}} in the {{GroupMetadataManager}} will not contain any information about the group 'Bob'. However, the {{offsetCache}} in the {{GroupMetadataManager}} will contain information about 'Bob'. Currently the only way for admin tools to know the full set of groups being managed by Kafka, i.e. those storing offsets in Kafka, those using Kafka for balancing of consumer groups, and those using Kafka for both, is to consume the offset topic. We need to extend the List/Describe groups API to allow admin tools to discover 'Bob' and allow the partition offsets to be retrieved. was: The {{ListGroupsRequest}} and {{DescribeGroupsRequest}} added to 0.9.0.0 allow admin tools to get details of consumer groups now that this information is not stored in ZK. The brokers also now store offset information for consumer groups. At present, there is no API for admin tools to discover the groups that brokers are storing offsets for. For example, if a consumer is using the new consumer api, is storing offsets in Kafka under the groupId 'Bob', but is using manual partition assignment, then the {{groupCache}} in the {{GroupMetadataManager}} will not contain any information about the group 'Bob'. However, the {{offsetCache}} in the {{GroupMetadataManager}} will contain information about 'Bob'. We need to extend the List/Describe groups API to allow admin tools to discover 'Bob' and allow the partition offsets to be retrieved. > Extend ListGroups and DescribeGroup APIs to cover offsets > - > > Key: KAFKA-2901 > URL: https://issues.apache.org/jira/browse/KAFKA-2901 > Project: Kafka > Issue Type: Improvement > Components: consumer >Affects Versions: 0.9.0.0 >Reporter: The Data Lorax >Assignee: Neha Narkhede > Fix For: 0.9.0.1 > > > The {{ListGroupsRequest}} and {{DescribeGroupsRequest}} added to 0.9.0.0 > allow admin tools to get details of consumer groups now that this information > is not stored in ZK. > The brokers also now store offset information for consumer groups. At > present, there is no API for admin tools to discover the groups that brokers > are storing offsets for. > For example, if a consumer is using the new consumer api, is storing offsets > in Kafka under the groupId 'Bob', but is using manual partition assignment, > then the {{groupCache}} in the {{GroupMetadataManager}} will not contain any > information about the group 'Bob'. However, the {{offsetCache}} in the > {{GroupMetadataManager}} will contain information about 'Bob'. > Currently the only way for admin tools to know the full set of groups being > managed by Kafka, i.e. those storing offsets in Kafka, those using Kafka for > balancing of consumer groups, and those using Kafka for both, is to consume > the offset topic. > We need to extend the List/Describe groups API to allow admin tools to > discover 'Bob' and allow the partition offsets to be retrieved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)