[
https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-4541:
Assignee: Manikumar (was: Ashish Singh)
> Add capability to create delegation token
>
[
https://issues.apache.org/jira/browse/KAFKA-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114219#comment-16114219
]
Manikumar commented on KAFKA-5647:
--
[~ijuma] [~onurkaraman] Are we going to refactor ZkUtils,
[
https://issues.apache.org/jira/browse/KAFKA-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114219#comment-16114219
]
Manikumar edited comment on KAFKA-5647 at 8/4/17 10:50 AM:
---
[~ijuma]
[
https://issues.apache.org/jira/browse/KAFKA-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127513#comment-16127513
]
Manikumar commented on KAFKA-5714:
--
ZK based topic creation/deletion doesn't go through ACL
[
https://issues.apache.org/jira/browse/KAFKA-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1821.
--
Resolution: Fixed
It is working in newer Kafka versions.
> Example shell scripts broken
>
[
https://issues.apache.org/jira/browse/KAFKA-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127676#comment-16127676
]
Manikumar commented on KAFKA-2206:
--
this looks like is a duplicate of KIP-133/ KAFKA-3267. If so, we can
[
https://issues.apache.org/jira/browse/KAFKA-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1832.
--
Resolution: Fixed
Fixed in KAFKA-1041
> Async Producer will cause 'java.net.SocketException: Too many
[
https://issues.apache.org/jira/browse/KAFKA-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2220.
--
Resolution: Fixed
This got fixed in KAFKA-4743 / KIP-122.
> Improvement: Could we support rewind by
[
https://issues.apache.org/jira/browse/KAFKA-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127737#comment-16127737
]
Manikumar commented on KAFKA-5714:
--
By default, the SSL user name will be of the form
[
https://issues.apache.org/jira/browse/KAFKA-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2283.
--
Resolution: Fixed
> scheduler exception on non-controller node when shutdown
>
[
https://issues.apache.org/jira/browse/KAFKA-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3087.
--
Resolution: Fixed
This doc issue was fixed in newer Kafka versions.
> Fix documentation for
[
https://issues.apache.org/jira/browse/KAFKA-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128831#comment-16128831
]
Manikumar commented on KAFKA-5714:
--
>>The point is, that I am expecting the same behavior, whether I put
[
https://issues.apache.org/jira/browse/KAFKA-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127078#comment-16127078
]
Manikumar commented on KAFKA-5734:
--
We can use JMAP command to output a histogram of java object heap.
[
https://issues.apache.org/jira/browse/KAFKA-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123074#comment-16123074
]
Manikumar commented on KAFKA-5714:
--
[~a...@confluent.io] From the code, I can see that we are allowing
[
https://issues.apache.org/jira/browse/KAFKA-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130145#comment-16130145
]
Manikumar commented on KAFKA-5734:
--
Most of the heap entries are related to metrics. May be related to
[
https://issues.apache.org/jira/browse/KAFKA-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-275.
-
Resolution: Fixed
This issue is fixed in latest versions. Please reopen if the issue still
exists.
>
[
https://issues.apache.org/jira/browse/KAFKA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-359.
-
Resolution: Fixed
This has been fixed in newer Kafka versions.
> Add message constructor that takes
[
https://issues.apache.org/jira/browse/KAFKA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-357.
-
Resolution: Duplicate
Zookeeper related code is getting refactored in KAFKA-5027/KAFKA-5501
> Refactor
[
https://issues.apache.org/jira/browse/KAFKA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-196.
-
Resolution: Fixed
Topic MAX_NAME_LENGTH is set to 249 is newer Kafka verions.
> Topic creation fails on
[
https://issues.apache.org/jira/browse/KAFKA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-236.
-
Resolution: Fixed
This can be achieved by using reset consumer group tool or
[
https://issues.apache.org/jira/browse/KAFKA-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-186.
-
Resolution: Fixed
CompressionType Java class added in newer Kafka version.
> no clean way to
[
https://issues.apache.org/jira/browse/KAFKA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-276.
-
Resolution: Fixed
This was fixed in newer Kafka versions.
> Enforce max.message.size on the total message
[
https://issues.apache.org/jira/browse/KAFKA-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2218.
--
Resolution: Duplicate
PR is available for KAFKA-4914.
> reassignment tool needs to parse and validate
[
https://issues.apache.org/jira/browse/KAFKA-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3389.
--
Resolution: Won't Fix
As mentioned in the previous comment, this may not be an issue. Pl reopen if
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083972#comment-16083972
]
Manikumar commented on KAFKA-1696:
--
[~guozhang] This got delayed due to some internal works. Will raise
[
https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083980#comment-16083980
]
Manikumar commented on KAFKA-1499:
--
[~sludwig] Yes, newly produced data will use latest
[
https://issues.apache.org/jira/browse/KAFKA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084244#comment-16084244
]
Manikumar commented on KAFKA-1499:
--
[~sludwig] yes, you can override on topic level for compression.type.
[
https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-4914:
-
Fix Version/s: 1.0.0
> Partition re-assignment tool should check types before persisting state in
>
Manikumar created KAFKA-5644:
Summary: Transient test failure:
ResetConsumerGroupOffsetTest.testResetOffsetsToZonedDateTime
Key: KAFKA-5644
URL: https://issues.apache.org/jira/browse/KAFKA-5644
Project:
[
https://issues.apache.org/jira/browse/KAFKA-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5644:
Assignee: Manikumar
> Transient test failure:
>
[
https://issues.apache.org/jira/browse/KAFKA-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133441#comment-16133441
]
Manikumar commented on KAFKA-5751:
--
Duplicate of KAFKA-5747
> Kafka cannot start; corrupted index
[
https://issues.apache.org/jira/browse/KAFKA-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4889.
--
Resolution: Invalid
> 2G8lc
> -
>
> Key: KAFKA-4889
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4847.
--
Resolution: Invalid
> 1Y30J
> -
>
> Key: KAFKA-4847
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4865.
--
Resolution: Invalid
> 2X8BF
> -
>
> Key: KAFKA-4865
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4951.
--
Resolution: Fixed
This scenario is handled in the Idempotent producer (KIP-98) released in Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4813.
--
Resolution: Invalid
> 2h6R1
> -
>
> Key: KAFKA-4813
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4803.
--
Resolution: Invalid
> OT6Y1
> -
>
> Key: KAFKA-4803
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4804.
--
Resolution: Invalid
> TdOZY
> -
>
> Key: KAFKA-4804
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4821.
--
Resolution: Invalid
> 9244L
> -
>
> Key: KAFKA-4821
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3796.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
>
[
https://issues.apache.org/jira/browse/KAFKA-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5737.
--
Resolution: Fixed
Fix Version/s: 1.0.0
0.11.0.1
> KafkaAdminClient thread
[
https://issues.apache.org/jira/browse/KAFKA-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3322.
--
Resolution: Won't Fix
Pl reopen if you think the issue still exists
> recurring errors
>
[
https://issues.apache.org/jira/browse/KAFKA-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5744:
Assignee: Manikumar (was: Colin P. McCabe)
> ShellTest: add tests for attempting to run
[
https://issues.apache.org/jira/browse/KAFKA-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5744:
Assignee: Colin P. McCabe (was: Manikumar)
> ShellTest: add tests for attempting to run
[
https://issues.apache.org/jira/browse/KAFKA-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134008#comment-16134008
]
Manikumar commented on KAFKA-5744:
--
ShellTest.testRunProgramWithErrorReturn is failing on my machine
cc
[
https://issues.apache.org/jira/browse/KAFKA-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4078.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
> VIP for Kafka doesn't
[
https://issues.apache.org/jira/browse/KAFKA-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2053.
--
Resolution: Won't Fix
Pl reopen if you think the requirement still exists
> Make initZk a protected
[
https://issues.apache.org/jira/browse/KAFKA-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1495.
--
Resolution: Won't Fix
> Kafka Example SimpleConsumerDemo
> -
>
>
[
https://issues.apache.org/jira/browse/KAFKA-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2231.
--
Resolution: Cannot Reproduce
Topic deletion is more stable in latest releases. Pl reopen if you think
[
https://issues.apache.org/jira/browse/KAFKA-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3953.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
> start kafka fail
>
[
https://issues.apache.org/jira/browse/KAFKA-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2093.
--
Resolution: Won't Fix
Scala producer is deprecated. Pl reopen if you think the issue still exists
>
[
https://issues.apache.org/jira/browse/KAFKA-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3327.
--
Resolution: Cannot Reproduce
mostly related to config issue. Pl reopen if you think the issue still
[
https://issues.apache.org/jira/browse/KAFKA-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3951.
--
Resolution: Cannot Reproduce
Pl reopen if you think the issue still exists
>
[
https://issues.apache.org/jira/browse/KAFKA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2296.
--
Resolution: Duplicate
> Not able to delete topic on latest kafka
>
[
https://issues.apache.org/jira/browse/KAFKA-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2289.
--
Resolution: Fixed
This has been fixed.
> KafkaProducer logs erroneous warning on startup
>
[
https://issues.apache.org/jira/browse/KAFKA-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3927.
--
Resolution: Later
Yes, These changes are done in KAFKA-615. Please reopen if the issue still
exists.
[
https://issues.apache.org/jira/browse/KAFKA-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137281#comment-16137281
]
Manikumar commented on KAFKA-3473:
--
@ijuma Is this covered in KAFKA-5135/KIP-143?
> Add controller
[
https://issues.apache.org/jira/browse/KAFKA-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3800.
--
Resolution: Cannot Reproduce
Please reopen if the issue still exists.
> java client can`t poll msg
[
https://issues.apache.org/jira/browse/KAFKA-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5547:
Assignee: Manikumar
> Return topic authorization failed if no topic describe access
>
[
https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4823.
--
Resolution: Won't Fix
Kafka Dropped support for Java 1.6 from 0.9 release. You can try Rest
[
https://issues.apache.org/jira/browse/KAFKA-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5401.
--
Resolution: Duplicate
> Kafka Over TLS Error - Failed to send SSL Close message - Broken Pipe
>
[
https://issues.apache.org/jira/browse/KAFKA-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3653.
--
Resolution: Fixed
Fixed in KAFKA-5135/KIP-143
> expose the queue size in ControllerChannelManager
>
[
https://issues.apache.org/jira/browse/KAFKA-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138257#comment-16138257
]
Manikumar commented on KAFKA-5590:
--
Current TopicCommand uses Zookeeper based deletion. This does not
[
https://issues.apache.org/jira/browse/KAFKA-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138257#comment-16138257
]
Manikumar edited comment on KAFKA-5590 at 8/23/17 11:56 AM:
Current
[
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-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-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-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-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-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 commented on KAFKA-5917:
--
This happens when you run Kafka-configs.sh script with new versions
[
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: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-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198453#comment-16198453
]
Manikumar commented on KAFKA-6042:
--
This may be related KAFKA-5970
> Kafka Request Handler deadlocks and
[
https://issues.apache.org/jira/browse/KAFKA-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198416#comment-16198416
]
Manikumar commented on KAFKA-6022:
--
Since 0.10.1.0, no need to pass --new-consumer option. You just need
[
https://issues.apache.org/jira/browse/KAFKA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198497#comment-16198497
]
Manikumar commented on KAFKA-6042:
--
It would we great if you can use KAFKA-5970 and validate in your
[
https://issues.apache.org/jira/browse/KAFKA-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4504.
--
Resolution: Fixed
Assignee: Manikumar
Fix Version/s: 1.0.0
> Details of retention.bytes
[
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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
1 - 100 of 980 matches
Mail list logo
