Yunze Xu
We should also migrate #1018 to master branch for future versions like 2.10.0.
What's your broker's config? I tried to reproduce this issue with a KoP standalone but it works well. Here are my configs in `conf/standalone.conf`: ```properties messagingProtocols=kafka kafkaListeners=PLAINTEXT://127.0.0.1:9092 brokerEntryMetadataInterceptors=org.apache.pulsar.common.intercept.AppendBrokerTimestampMetadataInterceptor,org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor brokerDeleteInactiveTopicsEnabled=false #...
``` 14:22:22.180 [cluster-service-coordinator-timer] ERROR org.apache.pulsar.functions.worker.MembershipManager - Failed to get status of coordinate topic persistent://public/functions/coordinate org.apache.pulsar.client.admin.PulsarAdminException: java.util.concurrent.CompletionException: org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector$RetryException: Could not complete the operation. Number of retries has been exhausted. Failed reason:...
It looks okay from the logs. What's wrong of your application? BTW, the `CoordinatorLoadInProgress (Broker: Coordinator load in progress)` is not a permanent error, it's just because the group coordinator...
@jiangtao7 I cannot find the transaction related configs in your broker.conf. ```properties brokerDeduplicationEnabled=true kafkaTransactionCoordinatorEnabled=true ``` Did you miss the comments here: https://github.com/streamnative/kop/issues/1415#issuecomment-1191002775?
I also see you configured the same advertised listener and listener ```properties kafkaAdvertisedListeners=PLAINTEXT://pulsar-broker-0.pulsar-broker.pulsar-poc.svc.cluster.local:9092 kafkaListeners=PLAINTEXT://pulsar-broker-0.pulsar-broker.pulsar-poc.svc.cluster.local:9092 ``` The `kafkaAdvertisedListeners` should be like the `advertised.listeners` while the `kafkaListeners` should be like the `listeners`...
I see your config (https://github.com/streamnative/kop/issues/1415#issuecomment-1204129891) is ```yaml messagingProtocols: "kafka" protocolHandlerDirectory: "./protocols" kafkaListeners: "PLAINTEXT://127.0.0.1:9092" allowAutoTopicCreationType: "partitioned" brokerDeleteInactiveTopicsEnabled: "false" brokerDeduplicationEnabled: "true" kafkaTransactionCoordinatorEnabled: "true" ``` You didn't expose the `kafkaAdvertisedListeners`. BTW, I found...
In addition, is this issue still only for Python client? Are you still able to connect your cluster via Go client or Java CLI (`kafka-console-consumer.sh`)? If yes, it would be...
For Kafka topics, please use Kafka's admin tools to delete them. ```bash ./bin/kafka-topics.sh --bootstrap-server localhost:9092 --delete --topic ```
> Do you want to encode the payload in another way, like adding the id of the Pulsar Schema ? Yes. See the **Interaction with Pulsar clients - Pulsar Producer...