Re: error: ... protocols are incompatible with those of existing members ??
https://issues.apache.org/jira/browse/KAFKA-3829 Thanks again Gwen.
Re: error: ... protocols are incompatible with those of existing members ??
More likely that we didn't think of documenting it :) Do you want to open a JIRA? or submit a doc patch? We should obviously document this limitation, but I'm thinking that the REST API could also validate that connector ID doesn't collide with the distributed worker group. On Mon, Jun 13, 2016 at 5:11 AM, Barry Kaplan wrote: > Thanks Gwen, that was exactly my problem. I had changed the value of the > group.id to the same value as the config name. But rereading the docs I did > not find any hint of that this would occur. Did I miss it somewhere? > > -barry
Re: error: ... protocols are incompatible with those of existing members ??
Thanks Gwen, that was exactly my problem. I had changed the value of the group.id to the same value as the config name. But rereading the docs I did not find any hint of that this would occur. Did I miss it somewhere? -barry
Re: error: ... protocols are incompatible with those of existing members ??
Actually, this is exactly what Connect is doing. KafkaConnect uses its own "consumer" protocol called "connect" to distribute tasks between the workers. The default group name for this is connect-cluster, but it is possible to override it in the connect-distributed.properties file. SinkTasks also have a consumer (to get data from Kafka...), which uses the normal consumer protocol. The name for this group is "connect-" followed by the connector name. The connector name is configured with the connector itself (configuration file or REST). If you somehow managed to give both groups the same name, or (less expected) your connector has yet another consumer group in the plugin itself with the same name, you will see the error you reported. On Sat, Jun 11, 2016 at 10:16 AM, Barry Kaplan wrote: > Thanks Dana, > > But this error is for a *single* process using the kafka-connect library. > It does not seem to make any sense that the kafka-connect library would > connect to the broker with two different protocols in the same process. Am > I misunderstanding something? > > On Fri, Jun 10, 2016 at 6:55 PM, Dana Powers wrote: > >> Barry - i believe the error refers to the consumer group "protocol" that is >> used to decide which partitions get assigned to which consumers. The way it >> works is that each consumer says it wants to join X group and it can >> support protocols (1, 2, 3...). The broker looks at all consumers in group >> X and picks a protocol that all can support. If there is no common protocol >> you would see this error. Example protocols are 'roundrobin' and 'range' . >> >> You should check the configuration of the group protocol for each consumer >> and also check that you don't have extra consumers in the group, perhaps >> because the group id is reused / common. >> >> Hope this helps, >> >> -Dana >> On Jun 10, 2016 4:24 AM, "Barry Kaplan" wrote: >> >> I delete the group using kafka-consumer-groups.sh --delete and still I get >> the error. >>
Re: error: ... protocols are incompatible with those of existing members ??
Thanks Dana, But this error is for a *single* process using the kafka-connect library. It does not seem to make any sense that the kafka-connect library would connect to the broker with two different protocols in the same process. Am I misunderstanding something? On Fri, Jun 10, 2016 at 6:55 PM, Dana Powers wrote: > Barry - i believe the error refers to the consumer group "protocol" that is > used to decide which partitions get assigned to which consumers. The way it > works is that each consumer says it wants to join X group and it can > support protocols (1, 2, 3...). The broker looks at all consumers in group > X and picks a protocol that all can support. If there is no common protocol > you would see this error. Example protocols are 'roundrobin' and 'range' . > > You should check the configuration of the group protocol for each consumer > and also check that you don't have extra consumers in the group, perhaps > because the group id is reused / common. > > Hope this helps, > > -Dana > On Jun 10, 2016 4:24 AM, "Barry Kaplan" wrote: > > I delete the group using kafka-consumer-groups.sh --delete and still I get > the error. >
RE: error: ... protocols are incompatible with those of existing members ??
> Date: Fri, 10 Jun 2016 16:54:47 +0530 > Subject: Re: error: ... protocols are incompatible with those of existing > members ?? > From: bkap...@memelet.com > To: users@kafka.apache.org > > I delete the group using kafka-consumer-groups.sh --delete and still I get > the error. MG>Barry...assuming this happens when you construct a request to KafkaServer..in your log you should see a message: MG>"Kafka request handler %d on broker %d handling request %s".format(id, brokerId, req) MG>what are the id, brokerID and req contents of the message?MG>thanks
Re: error: ... protocols are incompatible with those of existing members ??
Barry - i believe the error refers to the consumer group "protocol" that is used to decide which partitions get assigned to which consumers. The way it works is that each consumer says it wants to join X group and it can support protocols (1, 2, 3...). The broker looks at all consumers in group X and picks a protocol that all can support. If there is no common protocol you would see this error. Example protocols are 'roundrobin' and 'range' . You should check the configuration of the group protocol for each consumer and also check that you don't have extra consumers in the group, perhaps because the group id is reused / common. Hope this helps, -Dana On Jun 10, 2016 4:24 AM, "Barry Kaplan" wrote: I delete the group using kafka-consumer-groups.sh --delete and still I get the error.
Re: error: ... protocols are incompatible with those of existing members ??
I delete the group using kafka-consumer-groups.sh --delete and still I get the error.
Re: error: ... protocols are incompatible with those of existing members ??
I didn't really expect this to help, but still, I tried deleting /all/ topics and recreating them. But still my connect app will no longer run due to this error. Does this error even have anything to do with persisted state, or is the broker complaining about live client connections?
error: ... protocols are incompatible with those of existing members ??
I am getting this error: Attempt to join group connect-elasticsearch-indexer failed due to: The > group member's supported protocols are incompatible with those of existing > members. This is a single kafka-connect process consuming two topics. The brokers have never changed, and the version of the kafka libraries have never changed. What could cause this? I'm guessing this is uncommon as searches really only yield the code that emits the exception.
