[jira] [Commented] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202228#comment-14202228 ] Sam Meder commented on KAFKA-493: - Sorry, don't have that anymore - it's been too long > H

[jira] [Commented] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

[ https://issues.apache.org/jira/browse/KAFKA-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946076#comment-13946076 ] Sam Meder commented on KAFKA-1029: -- We've seen this as well (once or twice in ~4 months).

[jira] [Commented] (KAFKA-493) High CPU usage on inactive server

[ https://issues.apache.org/jira/browse/KAFKA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970427#comment-13970427 ] Sam Meder commented on KAFKA-493: - Do you know if VisualVM uses sampling to arrive at that

[jira] [Created] (KAFKA-1417) Very slow initial high-level consumer startup in low traffic/blocking fetch scenario

Sam Meder created KAFKA-1417: Summary: Very slow initial high-level consumer startup in low traffic/blocking fetch scenario Key: KAFKA-1417 URL: https://issues.apache.org/jira/browse/KAFKA-1417 Project: K

[jira] [Commented] (KAFKA-1417) Very slow initial high-level consumer startup in low traffic/blocking fetch scenario

[ https://issues.apache.org/jira/browse/KAFKA-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979211#comment-13979211 ] Sam Meder commented on KAFKA-1417: -- The simple, although not the most efficient solution

[jira] [Commented] (KAFKA-1417) Very slow initial high-level consumer startup in low traffic/blocking fetch scenario

[ https://issues.apache.org/jira/browse/KAFKA-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979267#comment-13979267 ] Sam Meder commented on KAFKA-1417: -- I think the timeout is somewhat arbitrary, but since

[jira] [Commented] (KAFKA-1417) Very slow initial high-level consumer startup in low traffic/blocking fetch scenario

[ https://issues.apache.org/jira/browse/KAFKA-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980651#comment-13980651 ] Sam Meder commented on KAFKA-1417: -- It should, let me take a look at the 0.8.1 code. > V

[jira] [Commented] (KAFKA-1417) Very slow initial high-level consumer startup in low traffic/blocking fetch scenario

[ https://issues.apache.org/jira/browse/KAFKA-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981825#comment-13981825 ] Sam Meder commented on KAFKA-1417: -- Looks fine in 0.8.1 > Very slow initial high-level

[jira] [Resolved] (KAFKA-1417) Very slow initial high-level consumer startup in low traffic/blocking fetch scenario

[ https://issues.apache.org/jira/browse/KAFKA-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder resolved KAFKA-1417. -- Resolution: Fixed Fix Version/s: 0.8.1 > Very slow initial high-level consumer startup in low tr

[jira] [Created] (KAFKA-1447) Controlled shutdown deadlock when trying to send state updates

Sam Meder created KAFKA-1447: Summary: Controlled shutdown deadlock when trying to send state updates Key: KAFKA-1447 URL: https://issues.apache.org/jira/browse/KAFKA-1447 Project: Kafka Issue T

[jira] [Commented] (KAFKA-1447) Controlled shutdown deadlock when trying to send state updates

[ https://issues.apache.org/jira/browse/KAFKA-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996532#comment-13996532 ] Sam Meder commented on KAFKA-1447: -- 0.8.0 > Controlled shutdown deadlock when trying to

[jira] [Commented] (KAFKA-1447) Controlled shutdown deadlock when trying to send state updates

[ https://issues.apache.org/jira/browse/KAFKA-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997524#comment-13997524 ] Sam Meder commented on KAFKA-1447: -- We'll be rolling out 0.8.1.1 soon, but since we can't

[jira] [Created] (KAFKA-1461) Replica fetcher threads do not implement any back-off behavior

Sam Meder created KAFKA-1461: Summary: Replica fetcher threads do not implement any back-off behavior Key: KAFKA-1461 URL: https://issues.apache.org/jira/browse/KAFKA-1461 Project: Kafka Issue T

[jira] [Updated] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1461: - Summary: Replica fetcher thread does not implement any back-off behavior (was: Replica fetcher threads d

[jira] [Commented] (KAFKA-1447) Controlled shutdown deadlock when trying to send state updates

[ https://issues.apache.org/jira/browse/KAFKA-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002177#comment-14002177 ] Sam Meder commented on KAFKA-1447: -- I don't have those logs anymore, should have grabbed

[jira] [Updated] (KAFKA-997) Provide a strict verification mode when reading configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-997: Resolution: Won't Fix Status: Resolved (was: Patch Available) > Provide a strict verification mode

[jira] [Commented] (KAFKA-997) Provide a strict verification mode when reading configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010310#comment-14010310 ] Sam Meder commented on KAFKA-997: - Looked at this a bit more a while ago and am just going

[jira] [Commented] (KAFKA-330) Add delete topic support

[ https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530293#comment-13530293 ] Sam Meder commented on KAFKA-330: - I've been doing a lot of manual resetting of data in Kaf

[jira] [Commented] (KAFKA-330) Add delete topic support

[ https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584725#comment-13584725 ] Sam Meder commented on KAFKA-330: - Any news on this? > Add delete topic su

[jira] [Created] (KAFKA-938) High CPU usage when more or less idle

Sam Meder created KAFKA-938: --- Summary: High CPU usage when more or less idle Key: KAFKA-938 URL: https://issues.apache.org/jira/browse/KAFKA-938 Project: Kafka Issue Type: Bug Components:

[jira] [Updated] (KAFKA-938) High CPU usage when more or less idle

[ https://issues.apache.org/jira/browse/KAFKA-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-938: Status: Patch Available (was: Open) > High CPU usage when more or less idle > -

[jira] [Updated] (KAFKA-938) High CPU usage when more or less idle

[ https://issues.apache.org/jira/browse/KAFKA-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-938: Attachment: timeunit.patch > High CPU usage when more or less idle > ---

[jira] [Created] (KAFKA-943) Move all configuration key string to constants

Sam Meder created KAFKA-943: --- Summary: Move all configuration key string to constants Key: KAFKA-943 URL: https://issues.apache.org/jira/browse/KAFKA-943 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-943) Move all configuration key string to constants

[ https://issues.apache.org/jira/browse/KAFKA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-943: Status: Patch Available (was: Open) > Move all configuration key string to constants >

[jira] [Updated] (KAFKA-943) Move all configuration key string to constants

[ https://issues.apache.org/jira/browse/KAFKA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-943: Attachment: configConstants.patch > Move all configuration key string to constants > ---

[jira] [Commented] (KAFKA-945) Problem with test to send a message and then consume it

[ https://issues.apache.org/jira/browse/KAFKA-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686490#comment-13686490 ] Sam Meder commented on KAFKA-945: - We had a similar issue and it was due to a change in con

[jira] [Created] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

Sam Meder created KAFKA-946: --- Summary: Kafka Hadoop Consumer fails when verifying message checksum Key: KAFKA-946 URL: https://issues.apache.org/jira/browse/KAFKA-946 Project: Kafka Issue Type: Bu

[jira] [Updated] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-946: Attachment: hadoop_consumer.patch > Kafka Hadoop Consumer fails when verifying message checksum > --

[jira] [Updated] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-946: Status: Patch Available (was: Open) Attached a patch that simply passes the full message buffer instead of

[jira] [Created] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

Sam Meder created KAFKA-956: --- Summary: High-level consumer fails to check topic metadata response for errors Key: KAFKA-956 URL: https://issues.apache.org/jira/browse/KAFKA-956 Project: Kafka Issu

[jira] [Updated] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-956: Status: Patch Available (was: Open) > High-level consumer fails to check topic metadata response for er

[jira] [Updated] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-956: Attachment: consumer_metadata_fetch.patch Patch to throw an exception if no partition info is available.

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693683#comment-13693683 ] Sam Meder commented on KAFKA-956: - Regarding 1. - how does the consumer recover from having

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694034#comment-13694034 ] Sam Meder commented on KAFKA-956: - Right, but the topic already exists at the time of failu

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694150#comment-13694150 ] Sam Meder commented on KAFKA-956: - Basically the scenario is (roughly): 1. Start consumer(

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694516#comment-13694516 ] Sam Meder commented on KAFKA-956: - Seems like we need to allow for rebalancing only a subse

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696789#comment-13696789 ] Sam Meder commented on KAFKA-956: - I guess we can carry my patch locally for now (we don't

[jira] [Commented] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696943#comment-13696943 ] Sam Meder commented on KAFKA-956: - I don't think it has anything to do with topic creation,

[jira] [Commented] (KAFKA-943) Move all configuration key string to constants

[ https://issues.apache.org/jira/browse/KAFKA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699027#comment-13699027 ] Sam Meder commented on KAFKA-943: - I would actually argue that it is easier on external "co

[jira] [Commented] (KAFKA-943) Move all configuration key string to constants

[ https://issues.apache.org/jira/browse/KAFKA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699128#comment-13699128 ] Sam Meder commented on KAFKA-943: - So we also have a config management system external to t

[jira] [Commented] (KAFKA-943) Move all configuration key string to constants

[ https://issues.apache.org/jira/browse/KAFKA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701803#comment-13701803 ] Sam Meder commented on KAFKA-943: - How about an option that turns on strict validation?

[jira] [Commented] (KAFKA-969) Need to prevent failure of rebalance when there are no brokers available when consumer comes up

[ https://issues.apache.org/jira/browse/KAFKA-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705971#comment-13705971 ] Sam Meder commented on KAFKA-969: - I feel that Kafka servers and clients should really not

[jira] [Created] (KAFKA-994) High level consumer doesn't throw an exception when the message it is trying to fetch exceeds the configured fetch size

Sam Meder created KAFKA-994: --- Summary: High level consumer doesn't throw an exception when the message it is trying to fetch exceeds the configured fetch size Key: KAFKA-994 URL: https://issues.apache.org/jira/browse/KA

[jira] [Updated] (KAFKA-994) High level consumer doesn't throw an exception when the message it is trying to fetch exceeds the configured fetch size

[ https://issues.apache.org/jira/browse/KAFKA-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-994: Description: The high level consumer code is supposed to throw an exception when it encounters a message th

[jira] [Updated] (KAFKA-994) High level consumer doesn't throw an exception when the message it is trying to fetch exceeds the configured fetch size

[ https://issues.apache.org/jira/browse/KAFKA-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-994: Fix Version/s: 0.8 Status: Patch Available (was: Open) > High level consumer doesn't throw a

[jira] [Updated] (KAFKA-994) High level consumer doesn't throw an exception when the message it is trying to fetch exceeds the configured fetch size

[ https://issues.apache.org/jira/browse/KAFKA-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-994: Attachment: messageSize.patch > High level consumer doesn't throw an exception when the message it is tr

[jira] [Created] (KAFKA-995) Enforce that the value for replica.fetch.max.bytes is always >= the value for message.max.bytes

Sam Meder created KAFKA-995: --- Summary: Enforce that the value for replica.fetch.max.bytes is always >= the value for message.max.bytes Key: KAFKA-995 URL: https://issues.apache.org/jira/browse/KAFKA-995 Pro

[jira] [Updated] (KAFKA-995) Enforce that the value for replica.fetch.max.bytes is always >= the value for message.max.bytes

[ https://issues.apache.org/jira/browse/KAFKA-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-995: Status: Patch Available (was: Open) > Enforce that the value for replica.fetch.max.bytes is always >= t

[jira] [Updated] (KAFKA-995) Enforce that the value for replica.fetch.max.bytes is always >= the value for message.max.bytes

[ https://issues.apache.org/jira/browse/KAFKA-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-995: Attachment: replica_fetch_size_config.patch > Enforce that the value for replica.fetch.max.bytes is alwa

[jira] [Commented] (KAFKA-994) High level consumer doesn't throw an exception when the message it is trying to fetch exceeds the configured fetch size

[ https://issues.apache.org/jira/browse/KAFKA-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726535#comment-13726535 ] Sam Meder commented on KAFKA-994: - Yea, I realized that after the initial write-up, the att

[jira] [Updated] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-881: Attachment: kafka-roll-0.8.patch > Kafka broker not respecting log.roll.hours >

[jira] [Commented] (KAFKA-881) Kafka broker not respecting log.roll.hours

[ https://issues.apache.org/jira/browse/KAFKA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726789#comment-13726789 ] Sam Meder commented on KAFKA-881: - Attached a version of this patch that applies against 0.

[jira] [Updated] (KAFKA-943) Move all configuration key string to constants

[ https://issues.apache.org/jira/browse/KAFKA-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-943: Resolution: Won't Fix Status: Resolved (was: Patch Available) Resolving this issue since the patch

[jira] [Created] (KAFKA-997) Provide a strict verification mode when reading configuration properties

Sam Meder created KAFKA-997: --- Summary: Provide a strict verification mode when reading configuration properties Key: KAFKA-997 URL: https://issues.apache.org/jira/browse/KAFKA-997 Project: Kafka I

[jira] [Updated] (KAFKA-997) Provide a strict verification mode when reading configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-997: Status: Patch Available (was: Open) > Provide a strict verification mode when reading configuration pro

[jira] [Updated] (KAFKA-997) Provide a strict verification mode when reading configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-997: Attachment: strict-verification.patch Add strict verification property and use it in tests and similar situa

[jira] [Updated] (KAFKA-997) Provide a strict verification mode when reading configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-997: Attachment: strict-verification-2.patch > Provide a strict verification mode when reading configuration

[jira] [Updated] (KAFKA-997) Provide a strict verification mode when reading configuration properties

[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-997: Attachment: (was: strict-verification.patch) > Provide a strict verification mode when reading confi

[jira] [Created] (KAFKA-1010) Concurrency issue in getCluster() causes rebalance failure and dead consumer

Sam Meder created KAFKA-1010: Summary: Concurrency issue in getCluster() causes rebalance failure and dead consumer Key: KAFKA-1010 URL: https://issues.apache.org/jira/browse/KAFKA-1010 Project: Kafka

[jira] [Updated] (KAFKA-1010) Concurrency issue in getCluster() causes rebalance failure and dead consumer

[ https://issues.apache.org/jira/browse/KAFKA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1010: - Attachment: get_cluster_0_8.patch Simply move getCluster() call intro retry loop and eliminate second cal

[jira] [Updated] (KAFKA-1010) Concurrency issue in getCluster() causes rebalance failure and dead consumer

[ https://issues.apache.org/jira/browse/KAFKA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1010: - Status: Patch Available (was: Open) > Concurrency issue in getCluster() causes rebalance failure and

[jira] [Commented] (KAFKA-1010) Concurrency issue in getCluster() causes rebalance failure and dead consumer

[ https://issues.apache.org/jira/browse/KAFKA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742354#comment-13742354 ] Sam Meder commented on KAFKA-1010: -- weird, patch -p1 -i get_cluster_0_8.patch worked, but

[jira] [Updated] (KAFKA-1010) Concurrency issue in getCluster() causes rebalance failure and dead consumer

[ https://issues.apache.org/jira/browse/KAFKA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1010: - Attachment: get_cluster_0_8_git.patch > Concurrency issue in getCluster() causes rebalance failure an

[jira] [Updated] (KAFKA-1010) Concurrency issue in getCluster() causes rebalance failure and dead consumer

[ https://issues.apache.org/jira/browse/KAFKA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1010: - Attachment: (was: get_cluster_0_8.patch) > Concurrency issue in getCluster() causes rebalance fai

[jira] [Commented] (KAFKA-1010) Concurrency issue in getCluster() causes rebalance failure and dead consumer

[ https://issues.apache.org/jira/browse/KAFKA-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742365#comment-13742365 ] Sam Meder commented on KAFKA-1010: -- Git formatted patch is now attached.

[jira] [Created] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

Sam Meder created KAFKA-1029: Summary: Zookeeper leader election stuck in ephemeral node retry loop Key: KAFKA-1029 URL: https://issues.apache.org/jira/browse/KAFKA-1029 Project: Kafka Issue Typ

[jira] [Updated] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

[ https://issues.apache.org/jira/browse/KAFKA-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1029: - Attachment: 0001-KAFKA-1029-Use-brokerId-instead-of-leaderId-when-tri.patch > Zookeeper leader electi

[jira] [Updated] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

[ https://issues.apache.org/jira/browse/KAFKA-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1029: - Status: Patch Available (was: Open) > Zookeeper leader election stuck in ephemeral node retry loop >

[jira] [Updated] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

[ https://issues.apache.org/jira/browse/KAFKA-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1029: - Attachment: (was: 0001-KAFKA-1029-Use-brokerId-instead-of-leaderId-when-tri.patch) > Zookeeper l

[jira] [Updated] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

[ https://issues.apache.org/jira/browse/KAFKA-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1029: - Attachment: 0002-KAFKA-1029-Use-brokerId-instead-of-leaderId-when-tri.patch > Zookeeper leader electi

[jira] [Commented] (KAFKA-1029) Zookeeper leader election stuck in ephemeral node retry loop

[ https://issues.apache.org/jira/browse/KAFKA-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751431#comment-13751431 ] Sam Meder commented on KAFKA-1029: -- Updated patch to also include moving the listener reg

[jira] [Updated] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-956: Resolution: Fixed Status: Resolved (was: Patch Available) I can confirm that this issue was fixed b

[jira] [Closed] (KAFKA-956) High-level consumer fails to check topic metadata response for errors

[ https://issues.apache.org/jira/browse/KAFKA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder closed KAFKA-956. --- > High-level consumer fails to check topic metadata response for errors >

[jira] [Created] (KAFKA-1062) Reading topic metadata from zookeeper leads to incompatible ordering of partition list

Sam Meder created KAFKA-1062: Summary: Reading topic metadata from zookeeper leads to incompatible ordering of partition list Key: KAFKA-1062 URL: https://issues.apache.org/jira/browse/KAFKA-1062 Project:

[jira] [Updated] (KAFKA-1062) Reading topic metadata from zookeeper leads to incompatible ordering of partition list

[ https://issues.apache.org/jira/browse/KAFKA-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1062: - Attachment: sorted.patch > Reading topic metadata from zookeeper leads to incompatible ordering of >

[jira] [Updated] (KAFKA-1062) Reading topic metadata from zookeeper leads to incompatible ordering of partition list

[ https://issues.apache.org/jira/browse/KAFKA-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-1062: - Status: Patch Available (was: Open) > Reading topic metadata from zookeeper leads to incompatible or

[jira] [Commented] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775988#comment-13775988 ] Sam Meder commented on KAFKA-946: - Rebased patch attached. > Kafka Hadoop

[jira] [Updated] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-946: Attachment: (was: hadoop_consumer.patch) > Kafka Hadoop Consumer fails when verifying message checks

[jira] [Updated] (KAFKA-946) Kafka Hadoop Consumer fails when verifying message checksum

[ https://issues.apache.org/jira/browse/KAFKA-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Meder updated KAFKA-946: Attachment: hadoop_consumer_1.patch > Kafka Hadoop Consumer fails when verifying message checksum >