You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/06/10 13:39:36 UTC

[GitHub] [pulsar] anvinjain commented on issue #10673: update-partitioned-topic fails for newly created geo-replicated topic

anvinjain commented on issue #10673:
URL: https://github.com/apache/pulsar/issues/10673#issuecomment-858631833


   @315157973 Here you are doing equivalent of list-partitioned-topics right? 
   `Awaitility.await().untilAsserted(() -&gt; assertEquals(admin2.topics().getPartitionedTopicList(namespace).get(0)                , persistentTopicName));`
   
   Notice this section in bug description
   > [Bug 2]: List topics in R2: ./pulsar-admin topics list geo-1/ns-1 Does not list partitions of t4 (they are listed in R1 where we originally created t4)
   list of topics (instead of partitioned topics) from the other cluster, admin2 in your case, does not have the list of partitions as per the original bug report, unless you have produced and consumed.
   
   Also to reproduce 
   > [Bug 1]: Update partitioned topic from R2: ./pulsar-admin topics update-partitioned-topic -p 6 persistent://geo-1/ns-1/t4 500 Error returned.
   Please try updating number of partitions from the other cluster before doing produce and consume on this topic.
   
   I hope this clarified repro steps for both of the issues and how you can change the unit test to reflect these
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org