[jira] [Created] (KAFKA-7548) KafkaConsumer should not throw away already fetched data for paused partitions.

Mayuresh Gharat created KAFKA-7548: -- Summary: KafkaConsumer should not throw away already fetched data for paused partitions. Key: KAFKA-7548 URL: https://issues.apache.org/jira/browse/KAFKA-7548 Pro

[jira] [Created] (KAFKA-7096) Consumer should drop the data for unassigned topic partitions

Mayuresh Gharat created KAFKA-7096: -- Summary: Consumer should drop the data for unassigned topic partitions Key: KAFKA-7096 URL: https://issues.apache.org/jira/browse/KAFKA-7096 Project: Kafka

[jira] [Created] (KAFKA-3720) Remove BufferExhaustException from doSend() in KafkaProducer

Mayuresh Gharat created KAFKA-3720: -- Summary: Remove BufferExhaustException from doSend() in KafkaProducer Key: KAFKA-3720 URL: https://issues.apache.org/jira/browse/KAFKA-3720 Project: Kafka

[jira] [Created] (KAFKA-3722) PlaintextChannelBuilder should not use ChannelBuilders.createPrincipalBuilder(configs) for creating instance of PrincipalBuilder

Mayuresh Gharat created KAFKA-3722: -- Summary: PlaintextChannelBuilder should not use ChannelBuilders.createPrincipalBuilder(configs) for creating instance of PrincipalBuilder Key: KAFKA-3722 URL: https://issues.

[jira] [Assigned] (KAFKA-3995) Add a new configuration "enable.comrpession.ratio.estimation" to the producer config

[ https://issues.apache.org/jira/browse/KAFKA-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-3995: -- Assignee: Mayuresh Gharat > Add a new configuration "enable.comrpession.ratio.estimatio

[jira] [Assigned] (KAFKA-2120) Add a request timeout to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-2120: -- Assignee: Mayuresh Gharat > Add a request timeout to NetworkClient > --

[jira] [Commented] (KAFKA-2024) Cleaner can generate unindexable log segments

[ https://issues.apache.org/jira/browse/KAFKA-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503401#comment-14503401 ] Mayuresh Gharat commented on KAFKA-2024: Shouldn't the offsetIndex.scala should ha

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540270#comment-14540270 ] Mayuresh Gharat commented on KAFKA-1554: This sounds interesting. We may try to re

[jira] [Created] (KAFKA-2253) Deadlock in delayed operation purgatory

Mayuresh Gharat created KAFKA-2253: -- Summary: Deadlock in delayed operation purgatory Key: KAFKA-2253 URL: https://issues.apache.org/jira/browse/KAFKA-2253 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2160) DelayedOperationPurgatory should remove the pair in watchersForKey with empty watchers list

[ https://issues.apache.org/jira/browse/KAFKA-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575390#comment-14575390 ] Mayuresh Gharat commented on KAFKA-2160: We hit a deadlock while running brokers w

[jira] [Commented] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644945#comment-15644945 ] Mayuresh Gharat commented on KAFKA-4362: [~jasong35] form the details that Joel ha

[jira] [Commented] (KAFKA-4362) Consumer can fail after reassignment of the offsets topic partition

[ https://issues.apache.org/jira/browse/KAFKA-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649485#comment-15649485 ] Mayuresh Gharat commented on KAFKA-4362: I did some more testing while reproducing

[jira] [Created] (KAFKA-4433) Kafka Controller Does not send a LeaderAndIsr to old leader of a topicPartition during reassignment, if the old leader is not a part of the new assigned replicas

Mayuresh Gharat created KAFKA-4433: -- Summary: Kafka Controller Does not send a LeaderAndIsr to old leader of a topicPartition during reassignment, if the old leader is not a part of the new assigned replicas Key: KAFKA-4433

[jira] [Created] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

Mayuresh Gharat created KAFKA-4454: -- Summary: Authorizer should also include the Principal generated by the PrincipalBuilder. Key: KAFKA-4454 URL: https://issues.apache.org/jira/browse/KAFKA-4454 Pro

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703758#comment-15703758 ] Mayuresh Gharat commented on KAFKA-4454: [~ijuma] [~jjkoshy] [~ashishsinghdev] [~p

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709335#comment-15709335 ] Mayuresh Gharat commented on KAFKA-4454: [~jjkoshy] [~ashishsinghdev] [~parth.brah

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713402#comment-15713402 ] Mayuresh Gharat commented on KAFKA-4454: [~ijuma] Thanks for pointing me to the pa

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716114#comment-15716114 ] Mayuresh Gharat commented on KAFKA-4454: [~ijuma] I might not be understanding "ac

[jira] [Comment Edited] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716114#comment-15716114 ] Mayuresh Gharat edited comment on KAFKA-4454 at 12/2/16 8:00 PM: ---

[jira] [Comment Edited] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716114#comment-15716114 ] Mayuresh Gharat edited comment on KAFKA-4454 at 12/2/16 8:13 PM: ---

[jira] [Commented] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730371#comment-15730371 ] Mayuresh Gharat commented on KAFKA-4454: [~junrao], thanks a lot for the review. T

[jira] [Commented] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886288#comment-15886288 ] Mayuresh Gharat commented on KAFKA-4808: [~ijuma] I was thinking if throwing "INVA

[jira] [Assigned] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-4808: -- Assignee: Mayuresh Gharat > send of null key to a compacted topic should throw error ba

[jira] [Commented] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886365#comment-15886365 ] Mayuresh Gharat commented on KAFKA-4808: [~ijuma] Sure we can provide a better err

[jira] [Commented] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935327#comment-15935327 ] Mayuresh Gharat commented on KAFKA-4808: [~ijuma] Please find the KIP here : htt

[jira] [Comment Edited] (KAFKA-4808) send of null key to a compacted topic should throw error back to user

[ https://issues.apache.org/jira/browse/KAFKA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935327#comment-15935327 ] Mayuresh Gharat edited comment on KAFKA-4808 at 3/21/17 9:00 PM: ---

[jira] [Commented] (KAFKA-1476) Get a list of consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275714#comment-14275714 ] Mayuresh Gharat commented on KAFKA-1476: Was just thinking if this can be exposed

[jira] [Updated] (KAFKA-1013) Modify existing tools as per the changes in KAFKA-1000

[ https://issues.apache.org/jira/browse/KAFKA-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1013: --- Attachment: KAFKA-1013_2015-01-13_13:56:39.patch > Modify existing tools as per the changes in

[jira] [Commented] (KAFKA-1013) Modify existing tools as per the changes in KAFKA-1000

[ https://issues.apache.org/jira/browse/KAFKA-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276025#comment-14276025 ] Mayuresh Gharat commented on KAFKA-1013: Updated reviewboard https://reviews.apach

[jira] [Updated] (KAFKA-1013) Modify existing tools as per the changes in KAFKA-1000

[ https://issues.apache.org/jira/browse/KAFKA-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1013: --- Description: Modify existing tools as per the changes in KAFKA-1000. AFAIK, the tools below w

[jira] [Resolved] (KAFKA-1785) Consumer offset checker should show the offset manager and offsets partition

[ https://issues.apache.org/jira/browse/KAFKA-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat resolved KAFKA-1785. Resolution: Duplicate > Consumer offset checker should show the offset manager and offsets p

[jira] [Commented] (KAFKA-1013) Modify existing tools as per the changes in KAFKA-1000

[ https://issues.apache.org/jira/browse/KAFKA-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276282#comment-14276282 ] Mayuresh Gharat commented on KAFKA-1013: Updated reviewboard https://reviews.apach

[jira] [Updated] (KAFKA-1013) Modify existing tools as per the changes in KAFKA-1000

[ https://issues.apache.org/jira/browse/KAFKA-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1013: --- Attachment: KAFKA-1013_2015-01-13_16:43:03.patch > Modify existing tools as per the changes in

[jira] [Commented] (KAFKA-853) Allow OffsetFetchRequest to initialize offsets

[ https://issues.apache.org/jira/browse/KAFKA-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285162#comment-14285162 ] Mayuresh Gharat commented on KAFKA-853: --- Hi Balaji Seshadri, I am trying to understa

[jira] [Assigned] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

[ https://issues.apache.org/jira/browse/KAFKA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-1860: -- Assignee: Mayuresh Gharat (was: Guozhang Wang) > File system errors are not detected u

[jira] [Assigned] (KAFKA-1796) Sanity check partition command line tools

[ https://issues.apache.org/jira/browse/KAFKA-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-1796: -- Assignee: Mayuresh Gharat > Sanity check partition command line tools > ---

[jira] [Commented] (KAFKA-1796) Sanity check partition command line tools

[ https://issues.apache.org/jira/browse/KAFKA-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319346#comment-14319346 ] Mayuresh Gharat commented on KAFKA-1796: [~nehanarkhede], I went over KAFKA-1678.

[jira] [Comment Edited] (KAFKA-1796) Sanity check partition command line tools

[ https://issues.apache.org/jira/browse/KAFKA-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319346#comment-14319346 ] Mayuresh Gharat edited comment on KAFKA-1796 at 2/13/15 1:07 AM: ---

[jira] [Commented] (KAFKA-1796) Sanity check partition command line tools

[ https://issues.apache.org/jira/browse/KAFKA-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333536#comment-14333536 ] Mayuresh Gharat commented on KAFKA-1796: [~nehanarkhede] Sure. Actually I went thr

[jira] [Assigned] (KAFKA-1998) Partitions Missing From MetadataResponse

[ https://issues.apache.org/jira/browse/KAFKA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-1998: -- Assignee: Mayuresh Gharat > Partitions Missing From MetadataResponse >

[jira] [Commented] (KAFKA-1998) Partitions Missing From MetadataResponse

[ https://issues.apache.org/jira/browse/KAFKA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347645#comment-14347645 ] Mayuresh Gharat commented on KAFKA-1998: I suppose what we need to do is top expos

[jira] [Created] (KAFKA-2014) Chaos Monkey / Failure Inducer for Kafka

Mayuresh Gharat created KAFKA-2014: -- Summary: Chaos Monkey / Failure Inducer for Kafka Key: KAFKA-2014 URL: https://issues.apache.org/jira/browse/KAFKA-2014 Project: Kafka Issue Type: Task

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361306#comment-14361306 ] Mayuresh Gharat commented on KAFKA-1554: So in this case we should be deleting the

[jira] [Comment Edited] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361306#comment-14361306 ] Mayuresh Gharat edited comment on KAFKA-1554 at 3/13/15 11:26 PM: --

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361309#comment-14361309 ] Mayuresh Gharat commented on KAFKA-1554: I can take a shot at this one. > Corrupt

[jira] [Assigned] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-1554: -- Assignee: Mayuresh Gharat > Corrupt index found on clean startup >

[jira] [Updated] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

[ https://issues.apache.org/jira/browse/KAFKA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1860: --- Attachment: KAFKA-1860.patch > File system errors are not detected unless Kafka tries to write

[jira] [Commented] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

[ https://issues.apache.org/jira/browse/KAFKA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366069#comment-14366069 ] Mayuresh Gharat commented on KAFKA-1860: Created reviewboard https://reviews.apach

[jira] [Updated] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

[ https://issues.apache.org/jira/browse/KAFKA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1860: --- Status: Patch Available (was: Open) > File system errors are not detected unless Kafka tries

[jira] [Commented] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

[ https://issues.apache.org/jira/browse/KAFKA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366088#comment-14366088 ] Mayuresh Gharat commented on KAFKA-1860: We need to reproduce and test the fix on

[jira] [Issue Comment Deleted] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

[ https://issues.apache.org/jira/browse/KAFKA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1860: --- Comment: was deleted (was: We need to reproduce and test the fix on our kafka server mp) > Fi

[jira] [Commented] (KAFKA-1778) Create new re-elect controller admin function

[ https://issues.apache.org/jira/browse/KAFKA-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370426#comment-14370426 ] Mayuresh Gharat commented on KAFKA-1778: I did not get : c) Broker x will rightfu

[jira] [Updated] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1554: --- Status: Patch Available (was: Open) > Corrupt index found on clean startup >

[jira] [Updated] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1554: --- Attachment: KAFKA-1554.patch > Corrupt index found on clean startup >

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377009#comment-14377009 ] Mayuresh Gharat commented on KAFKA-1554: Created reviewboard https://reviews.apach

[jira] [Commented] (KAFKA-2038) Unable to restart brokers after it went down with no space left on disk

[ https://issues.apache.org/jira/browse/KAFKA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380190#comment-14380190 ] Mayuresh Gharat commented on KAFKA-2038: I suppose this will involve manual interv

[jira] (KAFKA-1610) Local modifications to collections generated from mapValues will be lost

[ https://issues.apache.org/jira/browse/KAFKA-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847355#comment-15847355 ] Mayuresh Gharat commented on KAFKA-1610: [~jozi-k] sure. The patch has been availa

[jira] [Commented] (KAFKA-3367) Delete topic dont delete the complete log from kafka

[ https://issues.apache.org/jira/browse/KAFKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189676#comment-15189676 ] Mayuresh Gharat commented on KAFKA-3367: It takes time to delete the logs, dependi

[jira] [Commented] (KAFKA-3367) Delete topic dont delete the complete log from kafka

[ https://issues.apache.org/jira/browse/KAFKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189933#comment-15189933 ] Mayuresh Gharat commented on KAFKA-3367: Is automatic topic creation turned ON in

[jira] [Commented] (KAFKA-3367) Delete topic dont delete the complete log from kafka

[ https://issues.apache.org/jira/browse/KAFKA-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190206#comment-15190206 ] Mayuresh Gharat commented on KAFKA-3367: The client that are producing to the kafk

[jira] [Commented] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193448#comment-15193448 ] Mayuresh Gharat commented on KAFKA-3388: If the batch is retried and re-enqueued,

[jira] [Assigned] (KAFKA-3390) ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition

[ https://issues.apache.org/jira/browse/KAFKA-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-3390: -- Assignee: Mayuresh Gharat > ReplicaManager may infinitely try-fail to shrink ISR set of

[jira] [Commented] (KAFKA-3390) ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition

[ https://issues.apache.org/jira/browse/KAFKA-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195593#comment-15195593 ] Mayuresh Gharat commented on KAFKA-3390: Do you mean that even after the topic got

[jira] [Commented] (KAFKA-3294) Kafka REST API

[ https://issues.apache.org/jira/browse/KAFKA-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258438#comment-15258438 ] Mayuresh Gharat commented on KAFKA-3294: Are you thinking of exposing a rest endpo

[jira] [Commented] (KAFKA-3294) Kafka REST API

[ https://issues.apache.org/jira/browse/KAFKA-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258891#comment-15258891 ] Mayuresh Gharat commented on KAFKA-3294: [~sriharsha.sm] so this will be integrate

[jira] [Created] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" excepion, it should also remove the condition object from the waiters

Mayuresh Gharat created KAFKA-3651: -- Summary: Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" excepion, it should also remove the condition object from the waiters deque Key:

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269837#comment-15269837 ] Mayuresh Gharat commented on KAFKA-3651: [~ijuma] Yes just working on the unit tes

[jira] [Commented] (KAFKA-3651) Whenever the BufferPool throws a "Failed to allocate memory within the configured max blocking time" exception, it should also remove the condition object from the wait

[ https://issues.apache.org/jira/browse/KAFKA-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269937#comment-15269937 ] Mayuresh Gharat commented on KAFKA-3651: [~amandazhu19620...@gmail.com] did you in

[jira] [Commented] (KAFKA-2948) Kafka producer does not cope well with topic deletions

[ https://issues.apache.org/jira/browse/KAFKA-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047220#comment-15047220 ] Mayuresh Gharat commented on KAFKA-2948: Adding TTL would mean another user expose

[jira] [Created] (KAFKA-2975) The newtorkClient should request a metadata update after it gets an error in the handleResponse()

Mayuresh Gharat created KAFKA-2975: -- Summary: The newtorkClient should request a metadata update after it gets an error in the handleResponse() Key: KAFKA-2975 URL: https://issues.apache.org/jira/browse/KAFKA-297

[jira] [Updated] (KAFKA-2975) The newtorkClient should request a metadata update after it gets an error in the handleResponse()

[ https://issues.apache.org/jira/browse/KAFKA-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-2975: --- Description: Currently in data pipeline, 1) Lets say Mirror Maker requestTimeout is set to 2

[jira] [Updated] (KAFKA-2975) The newtorkClient should request a metadata update after it gets an error in the handleResponse()

[ https://issues.apache.org/jira/browse/KAFKA-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-2975: --- Description: Currently in data pipeline, 1) Lets say Mirror Maker requestTimeout is set to 2

[jira] [Created] (KAFKA-2976) Mirror maker dies if we delete a topic from destination cluster

Mayuresh Gharat created KAFKA-2976: -- Summary: Mirror maker dies if we delete a topic from destination cluster Key: KAFKA-2976 URL: https://issues.apache.org/jira/browse/KAFKA-2976 Project: Kafka

[jira] [Resolved] (KAFKA-2975) The newtorkClient should request a metadata update after it gets an error in the handleResponse()

[ https://issues.apache.org/jira/browse/KAFKA-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat resolved KAFKA-2975. Resolution: Not A Problem > The newtorkClient should request a metadata update after it gets

[jira] [Commented] (KAFKA-1860) File system errors are not detected unless Kafka tries to write

[ https://issues.apache.org/jira/browse/KAFKA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062409#comment-15062409 ] Mayuresh Gharat commented on KAFKA-1860: Cool. > File system errors are not detec

[jira] [Commented] (KAFKA-2887) TopicMetadataRequest creates topic if it does not exist

[ https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063131#comment-15063131 ] Mayuresh Gharat commented on KAFKA-2887: [~hachikuji] just wanted to be sure what

[jira] [Comment Edited] (KAFKA-2887) TopicMetadataRequest creates topic if it does not exist

[ https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063131#comment-15063131 ] Mayuresh Gharat edited comment on KAFKA-2887 at 12/18/15 12:02 AM: -

[jira] [Commented] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064365#comment-15064365 ] Mayuresh Gharat commented on KAFKA-2937: I ran a test with few commits behind trun

[jira] [Comment Edited] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064365#comment-15064365 ] Mayuresh Gharat edited comment on KAFKA-2937 at 12/18/15 6:21 PM: --

[jira] [Created] (KAFKA-3013) Display the topic-partition in the exception message for expired batches in recordAccumulator

Mayuresh Gharat created KAFKA-3013: -- Summary: Display the topic-partition in the exception message for expired batches in recordAccumulator Key: KAFKA-3013 URL: https://issues.apache.org/jira/browse/KAFKA-3013

[jira] [Commented] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070294#comment-15070294 ] Mayuresh Gharat commented on KAFKA-2937: [~rsivaram] This can occur if during dele

[jira] [Comment Edited] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070294#comment-15070294 ] Mayuresh Gharat edited comment on KAFKA-2937 at 12/23/15 11:21 PM: -

[jira] [Commented] (KAFKA-3040) Broker didn't report new data after change in leader

[ https://issues.apache.org/jira/browse/KAFKA-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071192#comment-15071192 ] Mayuresh Gharat commented on KAFKA-3040: Do you have the controller logs for the t

[jira] [Comment Edited] (KAFKA-3040) Broker didn't report new data after change in leader

[ https://issues.apache.org/jira/browse/KAFKA-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071192#comment-15071192 ] Mayuresh Gharat edited comment on KAFKA-3040 at 12/24/15 7:09 PM: --

[jira] [Commented] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081352#comment-15081352 ] Mayuresh Gharat commented on KAFKA-2937: [~djh] does your integration test check i

[jira] [Commented] (KAFKA-3040) Broker didn't report new data after change in leader

[ https://issues.apache.org/jira/browse/KAFKA-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081519#comment-15081519 ] Mayuresh Gharat commented on KAFKA-3040: At Linkedin, we do have a separate contro

[jira] [Commented] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081910#comment-15081910 ] Mayuresh Gharat commented on KAFKA-2937: Yes, that might be possible but it should

[jira] [Commented] (KAFKA-3062) Read from kafka replication to get data likely Version based

[ https://issues.apache.org/jira/browse/KAFKA-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081987#comment-15081987 ] Mayuresh Gharat commented on KAFKA-3062: Hi [~itismewxg], can you explain the usec

[jira] [Work started] (KAFKA-3013) Display the topic-partition in the exception message for expired batches in recordAccumulator

[ https://issues.apache.org/jira/browse/KAFKA-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3013 started by Mayuresh Gharat. -- > Display the topic-partition in the exception message for expired batches in

[jira] [Updated] (KAFKA-3013) Display the topic-partition in the exception message for expired batches in recordAccumulator

[ https://issues.apache.org/jira/browse/KAFKA-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-3013: --- Status: Patch Available (was: In Progress) > Display the topic-partition in the exception mes

[jira] [Work started] (KAFKA-1911) Log deletion on stopping replicas should be async

[ https://issues.apache.org/jira/browse/KAFKA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1911 started by Mayuresh Gharat. -- > Log deletion on stopping replicas should be async > ---

[jira] [Updated] (KAFKA-1911) Log deletion on stopping replicas should be async

[ https://issues.apache.org/jira/browse/KAFKA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat updated KAFKA-1911: --- Status: Patch Available (was: In Progress) > Log deletion on stopping replicas should be asyn

[jira] [Commented] (KAFKA-2887) TopicMetadataRequest creates topic if it does not exist

[ https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086470#comment-15086470 ] Mayuresh Gharat commented on KAFKA-2887: [~hachikuji] just wanted to know if we ha

[jira] [Commented] (KAFKA-3083) a soft failure in controller may leader a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089586#comment-15089586 ] Mayuresh Gharat commented on KAFKA-3083: [~fpj] can you shed some light on what yo

[jira] [Commented] (KAFKA-2410) Implement "Auto Topic Creation" client side and remove support from Broker side

[ https://issues.apache.org/jira/browse/KAFKA-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089686#comment-15089686 ] Mayuresh Gharat commented on KAFKA-2410: I would like to bump up discussion on thi

[jira] [Comment Edited] (KAFKA-2410) Implement "Auto Topic Creation" client side and remove support from Broker side

[ https://issues.apache.org/jira/browse/KAFKA-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089686#comment-15089686 ] Mayuresh Gharat edited comment on KAFKA-2410 at 1/8/16 6:48 PM:

[jira] [Assigned] (KAFKA-3083) a soft failure in controller may leader a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Gharat reassigned KAFKA-3083: -- Assignee: Mayuresh Gharat > a soft failure in controller may leader a topic partition i

[jira] [Commented] (KAFKA-3083) a soft failure in controller may leader a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098607#comment-15098607 ] Mayuresh Gharat commented on KAFKA-3083: That's a very good point, I will verify i

[jira] [Comment Edited] (KAFKA-3083) a soft failure in controller may leader a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098607#comment-15098607 ] Mayuresh Gharat edited comment on KAFKA-3083 at 1/14/16 6:34 PM: ---

[jira] [Commented] (KAFKA-3083) a soft failure in controller may leader a topic partition in an inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102259#comment-15102259 ] Mayuresh Gharat commented on KAFKA-3083: For your question regarding : If broker

  1   2   3   4   >