[jira] [Commented] (KAFKA-10802) Spurious log message when starting consumers

2023-05-29 Thread t oo (Jira)


[ 
https://issues.apache.org/jira/browse/KAFKA-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727029#comment-17727029
 ] 

t oo commented on KAFKA-10802:
--

[~frosiere] did u solve?

> Spurious log message when starting consumers
> 
>
> Key: KAFKA-10802
> URL: https://issues.apache.org/jira/browse/KAFKA-10802
> Project: Kafka
>  Issue Type: Improvement
>Affects Versions: 2.6.0
>Reporter: Mickael Maison
>Assignee: Guozhang Wang
>Priority: Major
> Fix For: 2.7.0, 2.6.1, 2.8.0
>
>
> Reported by Gary Russell in the [2.6.1 RC3 vote 
> thread|https://lists.apache.org/thread.html/r13d2c687b2fafbe9907fceb3d4f3cc6d5b34f9f36a7fcc985c38b506%40%3Cdev.kafka.apache.org%3E]
> I am seeing this on every consumer start:
> 2020-11-25 13:54:34.858  INFO 42250 --- [ntainer#0-0-C-1] 
> o.a.k.c.c.internals.AbstractCoordinator  : [Consumer 
> clientId=consumer-ktest26int-1, groupId=ktest26int] Rebalance failed.
> org.apache.kafka.common.errors.MemberIdRequiredException: The group member 
> needs to have a valid member id before actually entering a consumer group.
> Due to this change 
> https://github.com/apache/kafka/commit/16ec1793d53700623c9cb43e711f585aafd44dd4#diff-15efe9b844f78b686393b6c2e2ad61306c3473225742caed05c7edab9a138832R468
> I understand what a MemberIdRequiredException is, but the previous (2.6.0) 
> log (with exception.getMessage()) didn't stand out like the new one does 
> because it was all on one line.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (KAFKA-7306) Ability for producer to push to topic on remote server via ELB name

2018-08-17 Thread t oo (JIRA)


 [ 
https://issues.apache.org/jira/browse/KAFKA-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

t oo updated KAFKA-7306:

Summary: Ability for producer to push to topic on remote server via ELB 
name  (was: Ability for produce to push to topic on remote server)

> Ability for producer to push to topic on remote server via ELB name
> ---
>
> Key: KAFKA-7306
> URL: https://issues.apache.org/jira/browse/KAFKA-7306
> Project: Kafka
>  Issue Type: New Feature
>  Components: config, core, producer 
>Reporter: t oo
>Priority: Major
>
> One ec2 (hostA) with producer wants to push to a topic on a different ec2 
> (hostB). hostB has got an ELB (hostC) in front of it. From my experimentation 
> and reading docs online Kafka does not support hostA producer connecting to 
> ELB name (and letting the ELB redirect to the hostB ec2)'s topic.
> Other tool servers (Atlas, Hive.etc) allow hostA to reference remote ELB and 
> have the ELB direct the connection to hostB where the tool servers run.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (KAFKA-7306) Ability for produce to push to topic on remote server

2018-08-17 Thread t oo (JIRA)
t oo created KAFKA-7306:
---

 Summary: Ability for produce to push to topic on remote server
 Key: KAFKA-7306
 URL: https://issues.apache.org/jira/browse/KAFKA-7306
 Project: Kafka
  Issue Type: New Feature
  Components: config, core, producer 
Reporter: t oo


One ec2 (hostA) with producer wants to push to a topic on a different ec2 
(hostB). hostB has got an ELB (hostC) in front of it. From my experimentation 
and reading docs online Kafka does not support hostA producer connecting to ELB 
name (and letting the ELB redirect to the hostB ec2)'s topic.

Other tool servers (Atlas, Hive.etc) allow hostA to reference remote ELB and 
have the ELB direct the connection to hostB where the tool servers run.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)