[jira] [Created] (KAFKA-16510) java.lang.OutOfMemoryError in kafka-metadata-quorum.sh
HiroArai created KAFKA-16510:
Summary: java.lang.OutOfMemoryError in kafka-metadata-quorum.sh
Key: KAFKA-16510
URL: https://issues.apache.org/jira/browse/KAFKA-16510
Project: Kafka
Issue Type: Bug
Components: tools
Affects Versions: 3.4.1
Reporter: HiroArai
kafka-metadata-quorum is not available in SASL_PLAIN.
I got this error, I only use SASL_PLAIN. not use SSL.
I found a person with a similar situation, but he is using mTLS.
https://issues.apache.org/jira/browse/KAFKA-16006
{code:java}
sh-4.2$ /opt/kafka/bin/kafka-metadata-quorum.sh --bootstrap-server :9093 --command-config controller-admin.properties describe --replication
[2024-04-11 04:12:54,128] ERROR Uncaught exception in thread
‘kafka-admin-client-thread | adminclient-1':
(org.apache.kafka.common.utils.KafkaThread)
java.lang.OutOfMemoryError: Java heap space
at java.base/java.nio.HeapByteBuffer.(HeapByteBuffer.java:64)
at java.base/java.nio.ByteBuffer.allocate(ByteBuffer.java:363)
at
org.apache.kafka.common.memory.MemoryPool$1.tryAllocate(MemoryPool.java:30)
at
org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:102)
at
org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.receiveResponseOrToken(SaslClientAuthenticator.java:476)
at
org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.receiveKafkaResponse(SaslClientAuthenticator.java:573)
at
org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.authenticate(SaslClientAuthenticator.java:251)
at
org.apache.kafka.common.network.KafkaChannel.prepare(KafkaChannel.java:181)
at
org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:543)
at org.apache.kafka.common.network.Selector.poll(Selector.java:481)
at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:585)
at
org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.processRequests(KafkaAdminClient.java:1504)
at
org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.run(KafkaAdminClient.java:1435)
at java.base/java.lang.Thread.run(Thread.java:840)
org.apache.kafka.common.errors.TimeoutException: The AdminClient thread has
exited. Call: describeMetadataQuorum
java.util.concurrent.ExecutionException:
org.apache.kafka.common.errors.TimeoutException: The AdminClient thread has
exited. Call: describeMetadataQuorum
at
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
at
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
at
org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
at
org.apache.kafka.tools.MetadataQuorumCommand.handleDescribeReplication(MetadataQuorumCommand.java:158)
at
org.apache.kafka.tools.MetadataQuorumCommand.execute(MetadataQuorumCommand.java:106)
at
org.apache.kafka.tools.MetadataQuorumCommand.mainNoExit(MetadataQuorumCommand.java:62)
at
org.apache.kafka.tools.MetadataQuorumCommand.main(MetadataQuorumCommand.java:57)
Caused by: org.apache.kafka.common.errors.TimeoutException: The AdminClient
thread has exited. Call: describeMetadataQuorum {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-16006) mTLS authentication works for kafka-topic.sh but fails for kafka-metadata-quorum.sh
[
https://issues.apache.org/jira/browse/KAFKA-16006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835989#comment-17835989
]
HiroArai commented on KAFKA-16006:
--
mee too I saw same error in the test.
> mTLS authentication works for kafka-topic.sh but fails for
> kafka-metadata-quorum.sh
> ---
>
> Key: KAFKA-16006
> URL: https://issues.apache.org/jira/browse/KAFKA-16006
> Project: Kafka
> Issue Type: Bug
> Components: tools
>Affects Versions: 3.4.0
>Reporter: 10011
>Priority: Major
>
> The same client-ssl configuration works for kafka-topics.sh script but failed
> for kafka-metadata-quorum.sh during authentication. See details below
> {code:java}
> bash-4.2$ ./kafka-topics.sh --bootstrap-server localhost:11005
> --command-config /config/client-ssl.properties --describe --topic
> clientmTLSTest
> Topic: clientmTLSTest TopicId: dg7q11k6R2m2dgDSDGEfXw PartitionCount: 3
> ReplicationFactor: 3 Configs: segment.bytes=1073741824
> Topic: clientmTLSTest Partition: 0 Leader: 5 Replicas: 5,6,4
> Isr: 6,5,4
> Topic: clientmTLSTest Partition: 1 Leader: 6 Replicas: 6,4,5
> Isr: 6,4,5
> Topic: clientmTLSTest Partition: 2 Leader: 4 Replicas: 4,5,6
> Isr: 6,4,5
> bash-4.2$ ./kafka-metadata-quorum.sh --command-config
> /config/client-ssl.properties --bootstrap-server localhost:11005 describe
> --status
> [2023-12-13 21:19:55,500] ERROR Uncaught exception in thread
> 'kafka-admin-client-thread | adminclient-1':
> (org.apache.kafka.common.utils.KafkaThread)
> java.lang.OutOfMemoryError: Java heap space
> at java.base/java.nio.HeapByteBuffer.(HeapByteBuffer.java:64)
> at java.base/java.nio.ByteBuffer.allocate(ByteBuffer.java:363)
> at
> org.apache.kafka.common.memory.MemoryPool$1.tryAllocate(MemoryPool.java:30)
> at
> org.apache.kafka.common.network.NetworkReceive.readFrom(NetworkReceive.java:102)
> at
> org.apache.kafka.common.network.KafkaChannel.receive(KafkaChannel.java:452)
> at
> org.apache.kafka.common.network.KafkaChannel.read(KafkaChannel.java:402)
> at org.apache.kafka.common.network.Selector.attemptRead(Selector.java:674)
> at
> org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:576)
> at org.apache.kafka.common.network.Selector.poll(Selector.java:481)
> at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:560)
> at
> org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.processRequests(KafkaAdminClient.java:1413)
> at
> org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.run(KafkaAdminClient.java:1344)
> at java.base/java.lang.Thread.run(Thread.java:842)
> org.apache.kafka.common.errors.TimeoutException: The AdminClient thread has
> exited. Call: listNodes
> java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException: The AdminClient thread has
> exited. Call: listNodes
> at
> java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
> at
> java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
> at
> org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
> at
> org.apache.kafka.tools.MetadataQuorumCommand.handleDescribeStatus(MetadataQuorumCommand.java:167)
> at
> org.apache.kafka.tools.MetadataQuorumCommand.execute(MetadataQuorumCommand.java:106)
> at
> org.apache.kafka.tools.MetadataQuorumCommand.mainNoExit(MetadataQuorumCommand.java:55)
> at
> org.apache.kafka.tools.MetadataQuorumCommand.main(MetadataQuorumCommand.java:50)
> Caused by: org.apache.kafka.common.errors.TimeoutException: The AdminClient
> thread has exited. Call: listNodes
> bash-4.2$ tail /logs/kafka/server.log
> [2023-12-13 21:18:17,356] INFO [SocketServer listenerType=BROKER, nodeId=4]
> Failed authentication with /127.0.0.1
> (channelId=127.0.0.1:11005-127.0.0.1:42730-794) (SSL handshake failed)
> (org.apache.kafka.common.network.Selector)
> [2023-12-13 21:19:55,464] INFO [SocketServer listenerType=BROKER, nodeId=4]
> Failed authentication with /127.0.0.1
> (channelId=127.0.0.1:11005-127.0.0.1:39594-809) (SSL handshake failed)
> (org.apache.kafka.common.network.Selector)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-16310) ListOffsets doesn't report the offset with maxTimestamp anymore
[
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834129#comment-17834129
]
HiroArai commented on KAFKA-16310:
--
[~chia7712] [~omkreddy]
> [~ijuma] Are you worry about the 3.6.2? If so, the fixes are reverted
>already. see
[https://home.apache.org/~manikumar/kafka-3.6.2-rc2/RELEASE_NOTES.html]
This is my first time commenting on kafka's jira. I apologize if this is an
unnecessary question.
The fix for this bug is not mentioned in the release notes of 3.6.2-rc2.
Will this bug not be fixed in 3.6.2 ?
> ListOffsets doesn't report the offset with maxTimestamp anymore
> ---
>
> Key: KAFKA-16310
> URL: https://issues.apache.org/jira/browse/KAFKA-16310
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Emanuele Sabellico
>Assignee: Chia-Ping Tsai
>Priority: Blocker
> Fix For: 3.8.0
>
>
> Updated: This is confirmed a regression issue in v3.7.0.
> The impact of this issue is that when there is a batch containing records
> with timestamp not in order, the offset of the timestamp will be wrong.(ex:
> the timestamp for t0 should be mapping to offset 10, but will get offset 12..
> etc). It'll cause the time index is putting the wrong offset, so the result
> will be unexpected.
> ===
> The last offset is reported instead.
> A test in librdkafka (0081/do_test_ListOffsets) is failing an it's checking
> that the offset with the max timestamp is the middle one and not the last
> one. The tests is passing with 3.6.0 and previous versions
> This is the test:
> [https://github.com/confluentinc/librdkafka/blob/a6d85bdbc1023b1a5477b8befe516242c3e182f6/tests/0081-admin.c#L4989]
>
> there are three messages, with timestamps:
> {noformat}
> t0 + 100
> t0 + 400
> t0 + 250{noformat}
> and indices 0,1,2.
> then a ListOffsets with RD_KAFKA_OFFSET_SPEC_MAX_TIMESTAMP is done.
> it should return offset 1 but in 3.7.0 and trunk is returning offset 2
> Even after 5 seconds from producing it's still returning 2 as the offset with
> max timestamp.
> ProduceRequest and ListOffsets were sent to the same broker (2), the leader
> didn't change.
> {code:java}
> %7|1709134230.019|SEND|0081_admin#producer-3|
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ProduceRequest (v7,
> 206 bytes @ 0, CorrId 2) %7|1709134230.020|RECV|0081_admin#producer-3|
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received ProduceResponse
> (v7, 95 bytes, CorrId 2, rtt 1.18ms)
> %7|1709134230.020|MSGSET|0081_admin#producer-3|
> [thrd:localhost:39951/bootstrap]: localhost:39951/2:
> rdkafkatest_rnd22e8d8ec45b53f98_do_test_ListOffsets [0]: MessageSet with 3
> message(s) (MsgId 0, BaseSeq -1) delivered {code}
> {code:java}
> %7|1709134235.021|SEND|0081_admin#producer-2|
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ListOffsetsRequest
> (v7, 103 bytes @ 0, CorrId 7) %7|1709134235.022|RECV|0081_admin#producer-2|
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received
> ListOffsetsResponse (v7, 88 bytes, CorrId 7, rtt 0.54ms){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
