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 2020/08/05 20:24:25 UTC

[GitHub] [pulsar] Saswatibhoi opened a new issue #7763: Producers are Failing to Create when Connecting to a "Non-Persistent Partitioned Replicated" Topic

Saswatibhoi opened a new issue #7763:
URL: https://github.com/apache/pulsar/issues/7763


   We have found a bug, where the producers are failing to create when connecting to a "non-persistent partitioned replicated" topic. Looks like the replicator fails to start based on the logs we see on the broker logs. The producers connect fine when it is a "non-persistent partitioned" topic but not replicated.  
   
   **Logs**
   18:19:56.844 [pulsar-io-23-3] WARN  org.apache.pulsar.broker.service.ServerCnx - Failed to get Partitioned Metadata [/127.0.0.1:54694] non-persistent://xxxx/yyyyy/zzzzz: non-persistent://xxxx/yyyyy/zzzzz failed to start replicator for vmb-aws-us-west-2
   org.apache.pulsar.broker.service.BrokerServiceException$NamingException: non-persistent://xxxx/yyyyy/zzzzz failed to start replicator for vmb-aws-us-west-2
   


----------------------------------------------------------------
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



[GitHub] [pulsar] congbobo184 commented on issue #7763: Producers are Failing to Create when Connecting to a "Non-Persistent Partitioned Replicated" Topic

Posted by GitBox <gi...@apache.org>.
congbobo184 commented on issue #7763:
URL: https://github.com/apache/pulsar/issues/7763#issuecomment-766597391


   I haven't tested anything wrong with the current master branch. can you provide specific steps to reproduce? (topic name, namespace name, broker version, autoCreateTopicConfig and what you can think of).thanks.


----------------------------------------------------------------
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



[GitHub] [pulsar] congbobo184 edited a comment on issue #7763: Producers are Failing to Create when Connecting to a "Non-Persistent Partitioned Replicated" Topic

Posted by GitBox <gi...@apache.org>.
congbobo184 edited a comment on issue #7763:
URL: https://github.com/apache/pulsar/issues/7763#issuecomment-766597391


   I haven't tested anything wrong with the current master branch. can you provide specific steps to reproduce? (topic name, namespace name, broker version, autoCreateTopicConfig and what you can think of).thanks.
   
   When the cluster 1 create non-persistent partitioned topic, one producer look up topic from cluster 2, and the topic haven't replicate from cluster 1 to cluster2, when cluster 2 create one non-partitioned non-persistent topic and found cluster 1 have create this topic by partitioned topic then it will throw this 
   
   ```
   18:19:56.844 [pulsar-io-23-3] WARN org.apache.pulsar.broker.service.ServerCnx - Failed to get Partitioned Metadata [/127.0.0.1:54694] non-persistent://xxxx/yyyyy/zzzzz: non-persistent://xxxx/yyyyy/zzzzz failed to start replicator for us-west
   org.apache.pulsar.broker.service.BrokerServiceException$NamingException: non-persistent://xxxx/yyyyy/zzzzz failed to start replicator for us-west
   ```
   


----------------------------------------------------------------
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



[GitHub] [pulsar] congbobo184 edited a comment on issue #7763: Producers are Failing to Create when Connecting to a "Non-Persistent Partitioned Replicated" Topic

Posted by GitBox <gi...@apache.org>.
congbobo184 edited a comment on issue #7763:
URL: https://github.com/apache/pulsar/issues/7763#issuecomment-766597391


   I haven't tested anything wrong with the current master branch. can you provide specific steps to reproduce?
   
   When the cluster 1 create non-persistent partitioned topic, one producer look up topic from cluster 2, and the topic haven't replicate from cluster 1 to cluster2, when cluster 2 create one non-partitioned non-persistent topic and found cluster 1 have create this topic by partitioned topic then it will throw this 
   
   ```
   18:19:56.844 [pulsar-io-23-3] WARN org.apache.pulsar.broker.service.ServerCnx - Failed to get Partitioned Metadata [/127.0.0.1:54694] non-persistent://xxxx/yyyyy/zzzzz: non-persistent://xxxx/yyyyy/zzzzz failed to start replicator for us-west
   org.apache.pulsar.broker.service.BrokerServiceException$NamingException: non-persistent://xxxx/yyyyy/zzzzz failed to start replicator for us-west
   ```
   


----------------------------------------------------------------
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



[GitHub] [pulsar] congbobo184 commented on issue #7763: Producers are Failing to Create when Connecting to a "Non-Persistent Partitioned Replicated" Topic

Posted by GitBox <gi...@apache.org>.
congbobo184 commented on issue #7763:
URL: https://github.com/apache/pulsar/issues/7763#issuecomment-766597391


   I haven't tested anything wrong with the current master branch. can you provide specific steps to reproduce? (topic name, namespace name, broker version, autoCreateTopicConfig and what you can think of).thanks.


----------------------------------------------------------------
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