[
https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198271#comment-16198271
]
Manikumar commented on KAFKA-6022:
--
looks like you are using old consumer API on mirror maker. By
[
https://issues.apache.org/jira/browse/KAFKA-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189475#comment-16189475
]
Manikumar commented on KAFKA-6005:
--
PR: https://github.com/apache/kafka/pull/3957
> Reject JoinGroup
Manikumar created KAFKA-6005:
Summary: Reject JoinGroup request from first member with empty
protocol type/protocol list
Key: KAFKA-6005
URL: https://issues.apache.org/jira/browse/KAFKA-6005
Project:
[
https://issues.apache.org/jira/browse/KAFKA-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187287#comment-16187287
]
Manikumar edited comment on KAFKA-5734 at 10/1/17 6:02 AM:
---
[~jangbora] looking
[
https://issues.apache.org/jira/browse/KAFKA-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16186974#comment-16186974
]
Manikumar commented on KAFKA-5997:
--
We need to use min.insync.replicas to enforce durability guarantees.
[
https://issues.apache.org/jira/browse/KAFKA-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185754#comment-16185754
]
Manikumar commented on KAFKA-4712:
--
This can be related to KAFKA-5758
> kafka-reassign-partitions causes
[
https://issues.apache.org/jira/browse/KAFKA-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5369.
--
Resolution: Duplicate
Resolving this as duplicate of KAFKA-4764, KAFKA-5920
> Producer hangs on
[
https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-4914:
Assignee: (was: Manikumar)
> Partition re-assignment tool should check types before persisting
[
https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-4914:
Assignee: Manikumar
> Partition re-assignment tool should check types before persisting state in
[
https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-4914:
-
Priority: Major (was: Minor)
> Partition re-assignment tool should check types before persisting state
[
https://issues.apache.org/jira/browse/KAFKA-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182969#comment-16182969
]
Manikumar commented on KAFKA-5982:
--
Please check KAFKA-5917
> Kafka 0.9.0.1 doesn't start after delete
[
https://issues.apache.org/jira/browse/KAFKA-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5015.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-4764
> SASL/SCRAM authentication failures are
[
https://issues.apache.org/jira/browse/KAFKA-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5910.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-4764
> Kafka 0.11.0.1 Kafka consumer/producers
[
https://issues.apache.org/jira/browse/KAFKA-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5917.
--
Resolution: Won't Fix
These kinds of issues can be avoided once we completely move Kafka tools to
Java
[
https://issues.apache.org/jira/browse/KAFKA-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169714#comment-16169714
]
Manikumar edited comment on KAFKA-5917 at 9/18/17 7:56 AM:
---
This happens when
[
https://issues.apache.org/jira/browse/KAFKA-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169714#comment-16169714
]
Manikumar commented on KAFKA-5917:
--
This happens when you run Kafka-configs.sh script with new versions
[
https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168830#comment-16168830
]
Manikumar commented on KAFKA-5407:
--
from broker logs:
{code}
[2017-09-14 15:16:56,688] ERROR [Group
[
https://issues.apache.org/jira/browse/KAFKA-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167717#comment-16167717
]
Manikumar commented on KAFKA-3722:
--
[~mgharat] I think KIP-189/KAFKA-5783 addresses this issue. If you
[
https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4454.
--
Resolution: Fixed
This is covered in KIP-189/KAFKA-5783
> Authorizer should also include the Principal
[
https://issues.apache.org/jira/browse/KAFKA-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167363#comment-16167363
]
Manikumar commented on KAFKA-5407:
--
[~fvegaucr] Can you upload broker logs at the time of error?
>
[
https://issues.apache.org/jira/browse/KAFKA-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-5750:
-
Summary: Elevate log messages for denials to INFO in SimpleAclAuthorizer
class (was: Elevate log
[
https://issues.apache.org/jira/browse/KAFKA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3124.
--
Resolution: Fixed
KAFKA-3361 added support for generating protocol documentation page to Kafka
docs.
[
https://issues.apache.org/jira/browse/KAFKA-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5177.
--
Resolution: Won't Fix
As mentioned above, these are transient warning messages. Please reopen if you
[
https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2887.
--
Resolution: Fixed
> TopicMetadataRequest creates topic if it does not exist
>
[
https://issues.apache.org/jira/browse/KAFKA-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1834.
--
Resolution: Fixed
This was fixed in newer Kafka versions.
> No Response when handle
[
https://issues.apache.org/jira/browse/KAFKA-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1630.
--
Resolution: Cannot Reproduce
Closing inactive issue. Please reopen if you think the issue still exists
[
https://issues.apache.org/jira/browse/KAFKA-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162853#comment-16162853
]
Manikumar commented on KAFKA-2887:
--
As of 0.11.0.0, We added a "allow_auto_topic_creation" flag to the
[
https://issues.apache.org/jira/browse/KAFKA-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162803#comment-16162803
]
Manikumar commented on KAFKA-1921:
--
[~onurkaraman] Now we have a command-line tool to reset Consumer
[
https://issues.apache.org/jira/browse/KAFKA-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2319.
--
Resolution: Fixed
This was fixed in newer versions. Pl reopen if you think the issue still exists
>
[
https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1817.
--
Resolution: Fixed
Fixed in KAFKA-1737
> AdminUtils.createTopic vs kafka-topics.sh --create with
[
https://issues.apache.org/jira/browse/KAFKA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1608.
--
Resolution: Fixed
This was fixed in newer versions. Pl reopen if you think the issue still exists
>
[
https://issues.apache.org/jira/browse/KAFKA-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-251.
-
Resolution: Won't Fix
Closing inactive issue as per above comments.
> The ConsumerStats MBean's
[
https://issues.apache.org/jira/browse/KAFKA-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158559#comment-16158559
]
Manikumar commented on KAFKA-5855:
--
I am able to generate some lag. By default, consumer reads from
[
https://issues.apache.org/jira/browse/KAFKA-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5592.
--
Resolution: Duplicate
Marking this as duplicate of KAFKA-4493.
> Connection with plain client to
[
https://issues.apache.org/jira/browse/KAFKA-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4638.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-5686. PR Raised for KAFKA-5686
> Outdated and
[
https://issues.apache.org/jira/browse/KAFKA-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158405#comment-16158405
]
Manikumar commented on KAFKA-5850:
--
[~saurabhbidwai] This issue is not related to Kafka. You may want to
[
https://issues.apache.org/jira/browse/KAFKA-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3033.
--
Resolution: Duplicate
Resolving this as a duplicate of KAFKA-4914.
> Reassigning partition stuck in
[
https://issues.apache.org/jira/browse/KAFKA-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4190.
--
Resolution: Duplicate
Resolving this duplicated KAFKA-4914. KAFKA-4914 PR is being reviewed now.
>
[
https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4119.
--
Resolution: Cannot Reproduce
Please reopen if the issue still exists.
> Get topic offset with Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4020.
--
Resolution: Fixed
Please reopen if the issue still exists.
> Kafka consumer stop taking messages
[
https://issues.apache.org/jira/browse/KAFKA-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1993.
--
Resolution: Fixed
Resolving this as duplicate of KAFKA-5384
> Enable topic deletion as default
>
[
https://issues.apache.org/jira/browse/KAFKA-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3113.
--
Resolution: Cannot Reproduce
may be seed broker is different for different topics. simpleconsumer
[
https://issues.apache.org/jira/browse/KAFKA-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2022.
--
Resolution: Won't Fix
I think we need to catch the exception and retry with a new leader. Pl reopen
[
https://issues.apache.org/jira/browse/KAFKA-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2623.
--
Resolution: Fixed
Time-based log retention is enforced in KIP-33. Pl reopen if you think the
issue
[
https://issues.apache.org/jira/browse/KAFKA-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157395#comment-16157395
]
Manikumar edited comment on KAFKA-1455 at 9/7/17 7:22 PM:
--
listGroupOffsets
[
https://issues.apache.org/jira/browse/KAFKA-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16157395#comment-16157395
]
Manikumar edited comment on KAFKA-1455 at 9/7/17 7:01 PM:
--
This is has been added
[
https://issues.apache.org/jira/browse/KAFKA-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2166.
--
Resolution: Fixed
Deletion related issues are fixed in newer versions. Pl reopen if you think
the
[
https://issues.apache.org/jira/browse/KAFKA-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1563.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
> High packet rate
[
https://issues.apache.org/jira/browse/KAFKA-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-47.
Resolution: Fixed
Closing this umbrella JIRA as all tasks are resolved.
> Create topic support and new ZK
[
https://issues.apache.org/jira/browse/KAFKA-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-641.
-
Resolution: Fixed
This is not relevant in newer versions.
> ConsumerOffsetChecker breaks when using dns
[
https://issues.apache.org/jira/browse/KAFKA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-252.
-
Resolution: Fixed
These API were handled in newer versions.
> Generalize getOffsetsBefore API to a new
[
https://issues.apache.org/jira/browse/KAFKA-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-986.
-
Resolution: Cannot Reproduce
> Topic Consumption Across multiple instances of consumer groups
>
[
https://issues.apache.org/jira/browse/KAFKA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1093.
--
Resolution: Invalid
relavent part of the code is not available now. So closing this now.
>
[
https://issues.apache.org/jira/browse/KAFKA-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1197.
--
Resolution: Fixed
Size, LogStartOffset, LogEndOffset are exposed as metrics in newer verions.
> Count
[
https://issues.apache.org/jira/browse/KAFKA-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-805.
-
Resolution: Fixed
Not able to reproduce the issue. looks like this got fixed in newer versions.
>
[
https://issues.apache.org/jira/browse/KAFKA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1946.
--
Resolution: Fixed
> Fix various broker metrics
> --
>
> Key:
[
https://issues.apache.org/jira/browse/KAFKA-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1962.
--
Resolution: Fixed
> Restore delayed request metrics
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1505.
--
Resolution: Fixed
This was fixed in newer versions. Pl reopen if you think the issue still exists
>
[
https://issues.apache.org/jira/browse/KAFKA-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3059.
--
Resolution: Duplicate
This functionality is implemented in KAFKA-4743
> ConsumerGroupCommand should
[
https://issues.apache.org/jira/browse/KAFKA-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4264.
--
Resolution: Duplicate
This is related to KAFKA-4931. PR is available for KAFKA-4931.
>
[
https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4337.
--
Resolution: Won't Fix
> Create topic in multiple zookeepers with Kafka AdminUtils.CreateTopic JAVA
>
[
https://issues.apache.org/jira/browse/KAFKA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150144#comment-16150144
]
Manikumar commented on KAFKA-4337:
--
As mentioned by [~ijuma], create command creates a topic using ZK
[
https://issues.apache.org/jira/browse/KAFKA-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4411.
--
Resolution: Not A Problem
It is necessary to have the same principal name across all brokers for ZK
[
https://issues.apache.org/jira/browse/KAFKA-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4188.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
> compilation issues with
[
https://issues.apache.org/jira/browse/KAFKA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3647.
--
Resolution: Fixed
Closing as per above comments.
> Unable to set a ssl provider
>
[
https://issues.apache.org/jira/browse/KAFKA-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3079.
--
Resolution: Cannot Reproduce
Mostly related to config error. Pl reopen if you think the issue still
[
https://issues.apache.org/jira/browse/KAFKA-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2986.
--
Resolution: Fixed
Fixed in newer versions. Pl reopen if you think the issue still exists
> Consumer
[
https://issues.apache.org/jira/browse/KAFKA-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2897.
--
Resolution: Won't Fix
Closing inactive issue. Pl reopen if you think the issue still exists
> Class
[
https://issues.apache.org/jira/browse/KAFKA-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2842.
--
Resolution: Fixed
This was fixed in KAFKA-3719
> BrokerEndPoint regex does't support hostname with _
>
[
https://issues.apache.org/jira/browse/KAFKA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2343.
--
Resolution: Fixed
Javadocs updated in newer versions.
> Clarify KafkaConsumer.poll rebalance behavior
[
https://issues.apache.org/jira/browse/KAFKA-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1138.
--
Resolution: Fixed
> Remote producer uses the hostname defined in broker
>
[
https://issues.apache.org/jira/browse/KAFKA-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1920.
--
Resolution: Duplicate
Similar metrics are proposed in KAFKA-5746.
> Add a metric to count client side
[
https://issues.apache.org/jira/browse/KAFKA-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1402.
--
Resolution: Fixed
We have KafkaServerTestHarness, EmbeddedKafkaCluster, EmbeddedZookeeper helper
[
https://issues.apache.org/jira/browse/KAFKA-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1447.
--
Resolution: Fixed
Pl reopen if you think the issue still exists
> Controlled shutdown deadlock when
[
https://issues.apache.org/jira/browse/KAFKA-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-818.
-
Resolution: Duplicate
Similar metrics are proposed in KAFKA-5746.
> Request failure metrics on the Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1347.
--
Resolution: Duplicate
This is being fixed in KAFKA-5476.
> Create a system test for network partitions
[
https://issues.apache.org/jira/browse/KAFKA-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4520.
--
Resolution: Fixed
Fix Version/s: 0.11.0.0
> Kafka broker fails with not so user-friendly error
[
https://issues.apache.org/jira/browse/KAFKA-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-270.
-
Resolution: Won't Fix
Closing due to inactivity. Pl reopen if you think the issue still exists
> sync
[
https://issues.apache.org/jira/browse/KAFKA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1492.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
> Getting error when
[
https://issues.apache.org/jira/browse/KAFKA-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1632.
--
Resolution: Cannot Reproduce
Mostly related to Kafka version mismatch. Pl reopen if you think the
[
https://issues.apache.org/jira/browse/KAFKA-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1463.
--
Resolution: Won't Fix
Pl reopen if you think the issue still exists
> producer fails with
[
https://issues.apache.org/jira/browse/KAFKA-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-888.
-
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
> problems when shutting
[
https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1980.
--
Resolution: Won't Fix
[~ndimiduk] Agree. Updated the JIRA.
> Console consumer throws OutOfMemoryError
[
https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reopened KAFKA-1980:
--
> Console consumer throws OutOfMemoryError with large max-messages
>
[
https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16147595#comment-16147595
]
Manikumar commented on KAFKA-1980:
--
[~ndimiduk] Apologies for not giving a proper explanation.
[
https://issues.apache.org/jira/browse/KAFKA-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4297.
--
Resolution: Duplicate
Closing this as there is a latest PR for KAFKA-4931.
> Cannot Stop Kafka with
[
https://issues.apache.org/jira/browse/KAFKA-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3570.
--
Resolution: Fixed
> It'd be nice to line up display output in columns in ConsumerGroupCommand
>
[
https://issues.apache.org/jira/browse/KAFKA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1980.
--
Resolution: Fixed
Closing as per comments. Pl reopen if you think the issue still exists
> Console
[
https://issues.apache.org/jira/browse/KAFKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1675.
--
Resolution: Fixed
gradlew, gradlew.bat scripts are removed from repo. Pl reopen if you think the
[
https://issues.apache.org/jira/browse/KAFKA-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2173.
--
Resolution: Cannot Reproduce
Might have fixed in latest versions. Pl reopen if you think the issue
[
https://issues.apache.org/jira/browse/KAFKA-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1636.
--
Resolution: Won't Fix
ConsumerIterator waits for the data from the underlying stream. Pl reopen if
you
[
https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-4391:
-
Labels: windows (was: )
> On Windows, Kafka server stops with uncaught exception after coming back from
[
https://issues.apache.org/jira/browse/KAFKA-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4634.
--
Resolution: Fixed
Similar issue fixed in KAFKA-1387/Newer versions. Pl reopen if you think the
issue
[
https://issues.apache.org/jira/browse/KAFKA-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-4695:
-
Labels: windows (was: )
> Can't start Kafka server after Blue Screen
>
[
https://issues.apache.org/jira/browse/KAFKA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16145032#comment-16145032
]
Manikumar commented on KAFKA-5649:
--
Can you enable Kafka debug logs and SSL debugs logs
[
https://issues.apache.org/jira/browse/KAFKA-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-5764:
-
Summary: KafkaShortnamer should allow for case-insensitive matches (was:
KafkaShortnamer should allow
[
https://issues.apache.org/jira/browse/KAFKA-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5764:
Assignee: Manikumar
> KafkaShortnamer should allow for case-insensitive matches
>
[
https://issues.apache.org/jira/browse/KAFKA-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4869.
--
Resolution: Fixed
Assignee: Manikumar
> 0.10.2.0 release notes incorrectly include KIP-115
>
[
https://issues.apache.org/jira/browse/KAFKA-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4350.
--
Resolution: Won't Fix
Closing as per comments.
> Can't mirror from Kafka 0.9 to Kafka 0.10.1
>
[
https://issues.apache.org/jira/browse/KAFKA-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4109.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
> kafka client send msg
801 - 900 of 980 matches
Mail list logo
