Discussion on KIP-670 : Add ConsumerGroupCommand to delete static members

Hi All, I am new to the Kafka contribution community. I have picked up a jira ticket https://issues.apache.org/jira/browse/KAFKA-9440 which requires KIP. I have submitted KIP for it https://cwiki.apache.org/confluence/display/KAFKA/KIP-670%3A+Add+ConsumerGroupCommand+to+delete+static+members I a

Re: Need contributor access to Kafka Improvement Proposals

Hi Matthias, Can you please grant me contributor access to create KIP ? UserId : sndp2693 EmailId : sndp2...@gmail.com Regards, Sandeep On Thu, Sep 3, 2020 at 1:26 PM Sandeep Kumar wrote: > HI, > > Can you please grant me access to create KIP? > > Thanks, > Sandeep >

Need contributor access to Kafka Improvement Proposals

HI, Can you please grant me access to create KIP? Thanks, Sandeep

Need contributor access to Jira

Hi Team , Please guide me how I can request for the contributor access for jira so that I can assign some jira tickets to myself and contribute to the kafka community. Username: sndp2693 Email: sndp2...@gmail.com Full Name: Sandeep Kumar Thanks and Regards Sandeep

[jira] [Updated] (KAFKA-4616) Message loss is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle

[ https://issues.apache.org/jira/browse/KAFKA-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandeep kumar singh updated KAFKA-4616: --- Summary: Message loss is seen when kafka-producer-perf-test.sh is running and any

[jira] [Commented] (KAFKA-4616) Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between

[ https://issues.apache.org/jira/browse/KAFKA-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821003#comment-15821003 ] sandeep kumar singh commented on KAFKA-4616: thanks for reply. i applied

[jira] [Commented] (KAFKA-4610) getting error:Batch containing 3 record(s) expired due to timeout while requesting metadata from brokers for test2R2P2-1

[ https://issues.apache.org/jira/browse/KAFKA-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820941#comment-15820941 ] sandeep kumar singh commented on KAFKA-4610: thanks for the update.

[jira] [Commented] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820892#comment-15820892 ] sandeep kumar singh commented on KAFKA-1843: in step 4 when you bring K

[jira] [Commented] (KAFKA-4616) Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between

[ https://issues.apache.org/jira/browse/KAFKA-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820237#comment-15820237 ] sandeep kumar singh commented on KAFKA-4616: is there any way to add thi

[jira] [Created] (KAFKA-4616) Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between

sandeep kumar singh created KAFKA-4616: -- Summary: Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between Key: KAFKA-4616 URL: https://issues.apache.org

[jira] [Commented] (KAFKA-4610) getting error:Batch containing 3 record(s) expired due to timeout while requesting metadata from brokers for test2R2P2-1

[ https://issues.apache.org/jira/browse/KAFKA-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814494#comment-15814494 ] sandeep kumar singh commented on KAFKA-4610: thanks for reply. yes mos

[jira] [Created] (KAFKA-4610) getting error:Batch containing 3 record(s) expired due to timeout while requesting metadata from brokers for test2R2P2-1

sandeep kumar singh created KAFKA-4610: -- Summary: getting error:Batch containing 3 record(s) expired due to timeout while requesting metadata from brokers for test2R2P2-1 Key: KAFKA-4610 URL: https