[
https://issues.apache.org/jira/browse/KAFKA-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5905:
Assignee: Manikumar
> Remove PrincipalBuilder and DefaultPrincipalBuilder
>
[
https://issues.apache.org/jira/browse/KAFKA-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492006#comment-16492006
]
Manikumar commented on KAFKA-6956:
--
Existing Jira for this task :
[
https://issues.apache.org/jira/browse/KAFKA-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6929.
--
Resolution: Fixed
Fix Version/s: 2.0.0
Fixed via https://github.com/apache/kafka/pull/5060
>
[
https://issues.apache.org/jira/browse/KAFKA-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16491626#comment-16491626
]
Manikumar commented on KAFKA-6947:
--
By default mirror maker config property "abort.on.send.failure" is
[
https://issues.apache.org/jira/browse/KAFKA-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3649.
--
Resolution: Fixed
Requested features are added in KIP-133: Describe and Alter Configs Admin APIs
and
[
https://issues.apache.org/jira/browse/KAFKA-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6921.
--
Resolution: Fixed
> Remove old Scala producer and all related code, tests, and tools
>
Manikumar created KAFKA-6945:
Summary: Add support to allow users to acquire delegation tokens
for other users
Key: KAFKA-6945
URL: https://issues.apache.org/jira/browse/KAFKA-6945
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6862.
--
Resolution: Invalid
Please reopen the Jira with more details.
> test toolchain
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4505.
--
Resolution: Auto Closed
{color:#00}Closing inactive issue. Please reopen if you think the issue
[
https://issues.apache.org/jira/browse/KAFKA-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2036.
--
Resolution: Duplicate
Resolving this duplicate of KIP-235/KIP-302
> Consumer and broker have
[
https://issues.apache.org/jira/browse/KAFKA-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3793.
--
Resolution: Cannot Reproduce
{color:#00}Closing inactive issue. Please reopen if you think the
[
https://issues.apache.org/jira/browse/KAFKA-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6356.
--
Resolution: Not A Problem
old data is discarded after log retention period or when the log reaches
[
https://issues.apache.org/jira/browse/KAFKA-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2943.
--
Resolution: Auto Closed
> Transient Failure in kafka.producer.SyncProducerTest.testReachableServer
>
[
https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5432.
--
Resolution: Auto Closed
Closing inactive issue. Exceptions observed with deprecated scala clients.
[
https://issues.apache.org/jira/browse/KAFKA-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4419.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-3355.
> Unable to GetOffset when the ACL of
[
https://issues.apache.org/jira/browse/KAFKA-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1460.
--
Resolution: Auto Closed
Closing inactive issue. Please reopen if you think the issue still exists in
[
https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-3355:
-
Fix Version/s: 2.0.0
> GetOffsetShell command doesn't work with SASL enabled Kafka
>
[
https://issues.apache.org/jira/browse/KAFKA-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2174.
--
Resolution: Auto Closed
Closing inactive issue.
> Wrong TopicMetadata deserialization
>
[
https://issues.apache.org/jira/browse/KAFKA-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3345.
--
Resolution: Auto Closed
Closing as scala producer is removed from codebase.
[
https://issues.apache.org/jira/browse/KAFKA-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5039.
--
Resolution: Auto Closed
Closing as scala producer is removed from codebase.
> Logging in
[
https://issues.apache.org/jira/browse/KAFKA-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3246.
--
Resolution: Auto Closed
> Transient Failure in
>
[
https://issues.apache.org/jira/browse/KAFKA-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5728.
--
Resolution: Auto Closed
looks like this is related to spring kafka config issue. must be related to
[
https://issues.apache.org/jira/browse/KAFKA-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4091.
--
Resolution: Cannot Reproduce
{color:#00}Closing inactive issue. Please reopen if you think the
[
https://issues.apache.org/jira/browse/KAFKA-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3843.
--
Resolution: Auto Closed
The Scala consumers have been deprecated and no further work is planned, please
[
https://issues.apache.org/jira/browse/KAFKA-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3620.
--
Resolution: Fixed
Closing this as some cleanup done in newer versions. Please reopen if you
think
[
https://issues.apache.org/jira/browse/KAFKA-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3180.
--
Resolution: Not A Problem
I suggest to post these kind of queries to
[
https://issues.apache.org/jira/browse/KAFKA-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1977.
--
Resolution: Auto Closed
Closing this as the Scala consumers have been deprecated and no further work is
[
https://issues.apache.org/jira/browse/KAFKA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6426.
--
Resolution: Cannot Reproduce
This looks like configuration issue. Please reopen if you think the issue
[
https://issues.apache.org/jira/browse/KAFKA-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6682.
--
Resolution: Duplicate
Resolving this as duplicate of KAFKA-6260. Please reopen if the issue still
[
https://issues.apache.org/jira/browse/KAFKA-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474473#comment-16474473
]
Manikumar commented on KAFKA-6787:
--
This might have fixed in KAFKA-6870.
> enumerate SampledStat.samples
[
https://issues.apache.org/jira/browse/KAFKA-6787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-6787:
-
Description:
{code}
java.lang.NullPointerException at
[
https://issues.apache.org/jira/browse/KAFKA-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474101#comment-16474101
]
Manikumar commented on KAFKA-5907:
--
[~ijuma] I am able to generate Java 9 javadocs on trunk.
> Support
[
https://issues.apache.org/jira/browse/KAFKA-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6141.
--
Resolution: Fixed
Closing this as log level changed to debug in ZOOKEEPER-2795 / Zookeeper 3.4.12
>
[
https://issues.apache.org/jira/browse/KAFKA-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467896#comment-16467896
]
Manikumar commented on KAFKA-6885:
--
In case of topics, there is a difference between names of topic
[
https://issues.apache.org/jira/browse/KAFKA-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466911#comment-16466911
]
Manikumar commented on KAFKA-6881:
--
By default Kafka is configured to store the data logs to /tmp/
[
https://issues.apache.org/jira/browse/KAFKA-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3921.
--
Resolution: Auto Closed
Closing inactive issue. The old producer is no longer supported. Please upgrade
[
https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465471#comment-16465471
]
Manikumar commented on KAFKA-6762:
--
looks like this is related to KAFKA-6834
> log-cleaner thread
[
https://issues.apache.org/jira/browse/KAFKA-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-6394:
Assignee: Manikumar
> Prevent misconfiguration of advertised listeners
>
[
https://issues.apache.org/jira/browse/KAFKA-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6837.
--
Resolution: Information Provided
> Apache kafka broker got stopped.
>
[
https://issues.apache.org/jira/browse/KAFKA-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465460#comment-16465460
]
Manikumar commented on KAFKA-6837:
--
As discussed offline, I suggest you to post these kind of queries to
[
https://issues.apache.org/jira/browse/KAFKA-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464080#comment-16464080
]
Manikumar commented on KAFKA-6863:
--
Is this not related to KIP-235 / KAFKA-6195?
[
https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3417.
--
Resolution: Fixed
Assignee: Mickael Maison (was: Grant Henke)
Fix Version/s: 2.0.0
>
[
https://issues.apache.org/jira/browse/KAFKA-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459817#comment-16459817
]
Manikumar commented on KAFKA-3143:
--
>From 1.1.0 (KAFKA-5083), last ISR is preserved in ZK, irrespective
[
https://issues.apache.org/jira/browse/KAFKA-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459756#comment-16459756
]
Manikumar commented on KAFKA-4701:
--
Can this be resolved as duplicate of KAFKA-6810?
> Allow kafka
[
https://issues.apache.org/jira/browse/KAFKA-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-6835:
Assignee: Manikumar
> Enable topic unclean leader election to be enabled without controller change
[
https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442861#comment-16442861
]
Manikumar commented on KAFKA-6798:
--
Yes, rebalances are due to zookeeper disconnects. Since it is
[
https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442656#comment-16442656
]
Manikumar commented on KAFKA-6798:
--
It does look like zk session timeout issue. Not sure why happening
[
https://issues.apache.org/jira/browse/KAFKA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442490#comment-16442490
]
Manikumar commented on KAFKA-6335:
--
[~Sonia] Can you give more details? Are you seeing test failure or an
[
https://issues.apache.org/jira/browse/KAFKA-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442343#comment-16442343
]
Manikumar commented on KAFKA-5813:
--
This might have fixed in async zk controller changes.
> Unexpected
[
https://issues.apache.org/jira/browse/KAFKA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1716.
--
Resolution: Auto Closed
Closing inactive issue. The Scala consumers have been deprecated and no further
[
https://issues.apache.org/jira/browse/KAFKA-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5287.
--
Resolution: Cannot Reproduce
Closing inactive issue. Please reopen with more details., if you think the
[
https://issues.apache.org/jira/browse/KAFKA-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5262.
--
Resolution: Cannot Reproduce
Closing inactive issue. Please reopen with more details., if you think the
[
https://issues.apache.org/jira/browse/KAFKA-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3476.
--
Resolution: Won't Fix
Closing this as we can export the GC values and performance opts. Please
reopen
[
https://issues.apache.org/jira/browse/KAFKA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6107.
--
Resolution: Fixed
Fix Version/s: 1.1.0
This was fixed in KafkaZkClient changes work.
> SCRAM
[
https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441972#comment-16441972
]
Manikumar edited comment on KAFKA-6798 at 4/18/18 6:43 AM:
---
ISR is set to empty
[
https://issues.apache.org/jira/browse/KAFKA-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441972#comment-16441972
]
Manikumar commented on KAFKA-6798:
--
ISR is set to empty if all replicas are out of sync and unclean
[
https://issues.apache.org/jira/browse/KAFKA-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441820#comment-16441820
]
Manikumar commented on KAFKA-6404:
--
SocketServer error handling is improved in KAFKA-5607. This must have
[
https://issues.apache.org/jira/browse/KAFKA-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441366#comment-16441366
]
Manikumar commented on KAFKA-6479:
--
One of the option is to adjust "connections.max.idle.ms" config
[
https://issues.apache.org/jira/browse/KAFKA-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2661.
--
Resolution: Fixed
SelectorTest.testCloseConnectionInClosingState/testCloseOldestConnection tests
[
https://issues.apache.org/jira/browse/KAFKA-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-6778:
Assignee: Manikumar
> DescribeConfigs does not return error for non-existent topic
>
[
https://issues.apache.org/jira/browse/KAFKA-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4373.
--
Resolution: Cannot Reproduce
Closing inactive issue. Please reopen if you think the issue still exists
[
https://issues.apache.org/jira/browse/KAFKA-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2284.
--
Resolution: Auto Closed
The Scala consumers have been deprecated and no further work is planned, please
[
https://issues.apache.org/jira/browse/KAFKA-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4347.
--
Resolution: Invalid
Looks like this is related to Apache Storm Kafka connector. Request you raise
the
[
https://issues.apache.org/jira/browse/KAFKA-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4124.
--
Resolution: Duplicate
Some of these requirements are implemented in KIP-112/KIP-113. Pls raise new
[
https://issues.apache.org/jira/browse/KAFKA-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435598#comment-16435598
]
Manikumar commented on KAFKA-1786:
--
looks like this requirement is covered in Dynamic Broker config
[
https://issues.apache.org/jira/browse/KAFKA-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-611.
-
Resolution: Auto Closed
mirror.topics.whitelist/blacklist were part of old consumer. also these configs
[
https://issues.apache.org/jira/browse/KAFKA-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2339.
--
Resolution: Cannot Reproduce
Not able to reproduce on latest server. Please reopen if you think the
[
https://issues.apache.org/jira/browse/KAFKA-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2302.
--
Resolution: Auto Closed
Closing inactive issue. The old consumer is no longer supported, please upgrade
[
https://issues.apache.org/jira/browse/KAFKA-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-2021:
-
Description:
* We have kafka.server.KafkaConfigTest, KafkaConfigConfigDefTest and
kafka.unit.KafkaTest
[
https://issues.apache.org/jira/browse/KAFKA-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1643.
--
Resolution: Auto Closed
The Scala producers have been deprecated for a while and no further work is
[
https://issues.apache.org/jira/browse/KAFKA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1405.
--
Resolution: Fixed
Old Scala JSON usage is removed in new versions of Kafka
> Global
[
https://issues.apache.org/jira/browse/KAFKA-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4883.
--
Resolution: Fixed
Assignee: Manikumar
Fix Version/s: 1.2.0
> invalid client
[
https://issues.apache.org/jira/browse/KAFKA-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-6752:
Assignee: Manikumar
> Unclean leader election metric no longer working
>
[
https://issues.apache.org/jira/browse/KAFKA-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6413.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-6084.
>
[
https://issues.apache.org/jira/browse/KAFKA-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-6741:
-
Description:
debug logs:
{code}
[2018-04-03 14:51:33,365] DEBUG Added sensor with name
Manikumar created KAFKA-6741:
Summary: Transient test failure:
SslTransportLayerTest.testNetworkThreadTimeRecorded
Key: KAFKA-6741
URL: https://issues.apache.org/jira/browse/KAFKA-6741
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6716.
--
Resolution: Fixed
Fix Version/s: 1.2.0
> discardChannel should be released in
[
https://issues.apache.org/jira/browse/KAFKA-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6630.
--
Resolution: Fixed
Fix Version/s: 1.2.0
> Speed up the processing of
[
https://issues.apache.org/jira/browse/KAFKA-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6702.
--
Resolution: Fixed
> Wrong className in LoggerFactory.getLogger method
>
[
https://issues.apache.org/jira/browse/KAFKA-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6707.
--
Resolution: Fixed
> The default value for config of Type.LONG should be *L
>
[
https://issues.apache.org/jira/browse/KAFKA-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412512#comment-16412512
]
Manikumar commented on KAFKA-6705:
--
Existing JIRA: KAFKA-3539
> producer.send() should not block due to
[
https://issues.apache.org/jira/browse/KAFKA-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6676.
--
Resolution: Fixed
Fix Version/s: 1.1.0
> System tests do not handle ZK chroot properly with
[
https://issues.apache.org/jira/browse/KAFKA-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6680.
--
Resolution: Fixed
Fix Version/s: (was: 1.2.0)
1.1.0
> Fix config
[
https://issues.apache.org/jira/browse/KAFKA-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406717#comment-16406717
]
Manikumar edited comment on KAFKA-6682 at 3/20/18 5:14 PM:
---
Looks like this
[
https://issues.apache.org/jira/browse/KAFKA-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406717#comment-16406717
]
Manikumar commented on KAFKA-6682:
--
Looks like this fixed in :
[
https://issues.apache.org/jira/browse/KAFKA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405870#comment-16405870
]
Manikumar edited comment on KAFKA-6689 at 3/20/18 7:05 AM:
---
These temp files
[
https://issues.apache.org/jira/browse/KAFKA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405870#comment-16405870
]
Manikumar commented on KAFKA-6689:
--
There temp files will be deleted after file.delete.delay.ms (default:
[
https://issues.apache.org/jira/browse/KAFKA-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-6680:
Assignee: Manikumar
Fix Version/s: 1.2.0
PR: https://github.com/apache/kafka/pull/4731
>
Manikumar created KAFKA-6680:
Summary: Fix config initialization in DynamicBrokerConfig
Key: KAFKA-6680
URL: https://issues.apache.org/jira/browse/KAFKA-6680
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6338.
--
Resolution: Not A Problem
Closing this in-favor of RANGER-1964
> java.lang.NoClassDefFoundError:
[
https://issues.apache.org/jira/browse/KAFKA-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6596.
--
Resolution: Not A Problem
I suggest you to reach out kafka-manager mailing list/github community for
[
https://issues.apache.org/jira/browse/KAFKA-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403454#comment-16403454
]
Manikumar commented on KAFKA-6613:
--
This might have fixed in KAFKA-5758
> The controller shouldn't stop
[
https://issues.apache.org/jira/browse/KAFKA-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5187.
--
Resolution: Not A Problem
Please reopen if the issue still exists.
> producer.close() times out at 30
[
https://issues.apache.org/jira/browse/KAFKA-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4782.
--
Resolution: Not A Problem
> change chroot for a kafka instance
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3553.
--
Resolution: Auto Closed
{color:#00}Closing inactive issue. Please raise issue with kafka-python
[
https://issues.apache.org/jira/browse/KAFKA-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3550.
--
Resolution: Fixed
Closing as per above comment.
> Broker does not honor MetadataRequest api version;
[
https://issues.apache.org/jira/browse/KAFKA-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3238.
--
Resolution: Auto Closed
Closing inactive issue. old consumer client is no longer supported. In newer
[
https://issues.apache.org/jira/browse/KAFKA-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1106.
--
Resolution: Auto Closed
Relevant parts of the code is changed an similar exceptions are fixed in the
[
https://issues.apache.org/jira/browse/KAFKA-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16397208#comment-16397208
]
Manikumar commented on KAFKA-4027:
--
More details about similar exception are here:
[
https://issues.apache.org/jira/browse/KAFKA-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4984.
--
Resolution: Cannot Reproduce
{color:#00}Closing inactive issue. Please reopen if you think the
601 - 700 of 980 matches
Mail list logo
