Create topic on remote cluster for geo-replication

[Gilthoniel]

Hi,

Since we've upgraded to v4.0.1, the cluster trying to geo-replicate is unable to create the topic on the remote cluster. It seems to be related to PIP-370 but as you can see, we have the configuration set to true and we use exclusively non-partitioned topics:

$ cat conf/broker.conf | grep createTopic
createTopicToRemoteClusterForReplication=true

When enabling the geo-replication, the cluster that must replicate is throwing a lot of

14:27:13.875 [pulsar-io-3-22] INFO org.apache.pulsar.client.impl.ConnectionPool - [[id: 0xdc7a9112, L:/***:33270 - R:cluster-***/***:6651]] Connected to server
14:27:13.911 [pulsar-io-3-20] ERROR org.apache.pulsar.client.impl.ClientCnx - [id: 0xc67d9284, L:/***:33256 - R:***/***:6651] Close connection because received internal-server error {"errorMsg":"","reqId":956378608433565193, "remote":"***/***:6651", "local":"/***:45300"}
14:27:13.912 [pulsar-io-3-20] WARN org.apache.pulsar.client.impl.BinaryProtoLookupService - [***] failed to get Partitioned metadata : {"errorMsg":"{"errorMsg":"","reqId":956378608433565193, "remote":"***/***:6651", "local":"/***:45300"}","reqId":2933251115940051830, "remote":"***/***:6651", "local":"/***:33256"}
org.apache.pulsar.client.api.PulsarClientException$LookupException: {"errorMsg":"{"errorMsg":"","reqId":956378608433565193, "remote":"***/***:6651", "local":"/***:45300"}","reqId":2933251115940051830, "remote":"***/***:6651", "local":"/***:33256"}

and on the remote broker:

14:28:03.131 [pulsar-proxy-io-2-10] WARN org.apache.pulsar.proxy.server.LookupProxyHandler - [***] failed to get Partitioned metadata : {"errorMsg":"","reqId":3883812047867488392, "remote":"***/***:6651", "local":"/***:51364"}
org.apache.pulsar.client.api.PulsarClientException$TopicDoesNotExistException: {"errorMsg":"","reqId":3883812047867488392, "remote":"***/***:6651", "local":"/***:51364"}
at org.apache.pulsar.client.impl.ClientCnx.getPulsarClientException(ClientCnx.java:1360) ~[org.apache.pulsar-pulsar-client-original-4.0.1.jar:4.0.1]

I am surprised because the flag is supposed to skip the fetch of the partitioned metadata but it seems to still trying to.

Any idea if I forgot to change a configuration or something when upgrading from the v3.0.x to v4.0.1 ?