[
https://issues.apache.org/jira/browse/KAFKA-14698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690451#comment-17690451
]
Demetrius Kellum commented on KAFKA-14698:
------------------------------------------
I encountered a similar issue. I was upgrading to the latest Kafka release for
a three broker cluster. When I started testing, my logs contained
InvalidRequestExceptions but the api key is different.
I ran the api version script and received this for ONLY one broker:
(id: 3 rack: null) -> (
Produce(0): UNSUPPORTED,
Fetch(1): 0 to 13 [usable: 13],
ListOffsets(2): UNSUPPORTED,
Metadata(3): UNSUPPORTED,
LeaderAndIsr(4): UNSUPPORTED,
StopReplica(5): UNSUPPORTED,
UpdateMetadata(6): UNSUPPORTED,
ControlledShutdown(7): 0 to 3 [usable: 3],
OffsetCommit(8): UNSUPPORTED,
OffsetFetch(9): UNSUPPORTED,
FindCoordinator(10): UNSUPPORTED,
JoinGroup(11): UNSUPPORTED,
Heartbeat(12): UNSUPPORTED,
LeaveGroup(13): UNSUPPORTED,
SyncGroup(14): UNSUPPORTED,
DescribeGroups(15): UNSUPPORTED,
ListGroups(16): UNSUPPORTED,
SaslHandshake(17): 0 to 1 [usable: 1],
ApiVersions(18): 0 to 3 [usable: 3],
CreateTopics(19): 0 to 7 [usable: 7],
DeleteTopics(20): 0 to 6 [usable: 6],
DeleteRecords(21): UNSUPPORTED,
InitProducerId(22): UNSUPPORTED,
OffsetForLeaderEpoch(23): UNSUPPORTED,
AddPartitionsToTxn(24): UNSUPPORTED,
AddOffsetsToTxn(25): UNSUPPORTED,
EndTxn(26): UNSUPPORTED,
WriteTxnMarkers(27): UNSUPPORTED,
TxnOffsetCommit(28): UNSUPPORTED,
DescribeAcls(29): 0 to 3 [usable: 3],
CreateAcls(30): 0 to 3 [usable: 3],
DeleteAcls(31): 0 to 3 [usable: 3],
DescribeConfigs(32): UNSUPPORTED,
AlterConfigs(33): 0 to 2 [usable: 2],
AlterReplicaLogDirs(34): UNSUPPORTED,
DescribeLogDirs(35): UNSUPPORTED,
SaslAuthenticate(36): 0 to 2 [usable: 2],
CreatePartitions(37): 0 to 3 [usable: 3],
CreateDelegationToken(38): UNSUPPORTED,
RenewDelegationToken(39): UNSUPPORTED,
ExpireDelegationToken(40): UNSUPPORTED,
DescribeDelegationToken(41): UNSUPPORTED,
DeleteGroups(42): UNSUPPORTED,
ElectLeaders(43): 0 to 2 [usable: 2],
IncrementalAlterConfigs(44): 0 to 1 [usable: 1],
AlterPartitionReassignments(45): 0 [usable: 0],
ListPartitionReassignments(46): 0 [usable: 0],
OffsetDelete(47): UNSUPPORTED,
DescribeClientQuotas(48): UNSUPPORTED,
AlterClientQuotas(49): 0 to 1 [usable: 1],
DescribeUserScramCredentials(50): UNSUPPORTED,
AlterUserScramCredentials(51): UNSUPPORTED,
Vote(52): 0 [usable: 0],
BeginQuorumEpoch(53): 0 [usable: 0],
EndQuorumEpoch(54): 0 [usable: 0],
DescribeQuorum(55): 0 to 1 [usable: 1],
AlterPartition(56): 0 to 2 [usable: 2],
UpdateFeatures(57): 0 to 1 [usable: 1],
Envelope(58): 0 [usable: 0],
FetchSnapshot(59): 0 [usable: 0],
DescribeCluster(60): UNSUPPORTED,
DescribeProducers(61): UNSUPPORTED,
BrokerRegistration(62): 0 [usable: 0],
BrokerHeartbeat(63): 0 [usable: 0],
UnregisterBroker(64): 0 [usable: 0],
DescribeTransactions(65): UNSUPPORTED,
ListTransactions(66): UNSUPPORTED,
AllocateProducerIds(67): 0 [usable: 0]
)
It seems like only one broker had this issue.
> Received request api key LEADER_AND_ISR which is not enabled
> ------------------------------------------------------------
>
> Key: KAFKA-14698
> URL: https://issues.apache.org/jira/browse/KAFKA-14698
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Affects Versions: 3.4.0
> Reporter: Mickael Maison
> Assignee: Akhilesh Chaganti
> Priority: Major
> Fix For: 3.5.0, 3.4.1
>
> Attachments: broker0.log, controller.log, test_online_migration.tar.gz
>
>
> I started from a Kafka cluster (with ZooKeeper) with 2 brokers. There's a
> single topic "test" with 2 partitions and 2 replicas and the internal
> __consumer_offsets topics.
> While following the ZooKeeper to KRaft migration steps from
> [https://kafka.apache.org/documentation/#kraft_zk_migration], I'm hitting
> issues at the Migrating brokers to KRaft step.
> When I restart a broker as KRaft, it repetitively prints the following error:
> {code:java}
> org.apache.kafka.common.errors.InvalidRequestException: Received request api
> key LEADER_AND_ISR which is not enabled
> [2023-02-09 16:14:30,334] ERROR Closing socket for
> 192.168.1.11:9092-192.168.1.11:63737-371 because of error
> (kafka.network.Processor)
> {code}
> The controller repetitively prints the following error:
> {code:java}
> [2023-02-09 16:12:27,456] WARN [Controller id=1000, targetBrokerId=0]
> Connection to node 0 (mmaison-mac.home/192.168.1.11:9092) could not be
> established. Broker may not be available.
> (org.apache.kafka.clients.NetworkClient)
> [2023-02-09 16:12:27,456] INFO [Controller id=1000, targetBrokerId=0] Client
> requested connection close from node 0
> (org.apache.kafka.clients.NetworkClient)
> [2023-02-09 16:12:27,560] INFO [Controller id=1000, targetBrokerId=0] Node 0
> disconnected. (org.apache.kafka.clients.NetworkClient)
> {code}
> Attached the controller logs and logs from broker-0
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
