This message was deleted.

It looks

__change _evenet

topics partitions are created weirdly.

I tested this on 2.10 and did not see these special topics. Here is the behaviour I am seeing. The original non-partitioned topic will be created as a partitioned topic with default number of partitions on the remote cluster. If you don’t have special logic to propagate partitioned topics (my recollections I saw the code does that but I tested on 2.10 still does not have the feature) Any partitioned topics on the original cluster, these will be created as a non-partitioned topic on the remote cluster.

Thanks for your answer, in my case I enforced the topics of the remote cluster to be partitioned.