You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2022/10/14 13:11:14 UTC

[GitHub] [rocketmq] fuyou001 opened a new issue, #5322: improving SDK topic route availability, when namsrv restart

fuyou001 opened a new issue, #5322:
URL: https://github.com/apache/rocketmq/issues/5322

   The issue tracker is used for bug reporting purposes **ONLY** whereas feature request needs to follow the [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal). To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
   
   It is recommended to start a discussion thread in the [mailing lists](http://rocketmq.apache.org/about/contact/) in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
   We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
   
   Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
   
   Generally, fixing an issue goes through the following steps:
   1. Understand the issue reported;
   1. Reproduce the unexpected behavior locally;
   1. Perform root cause analysis to identify the underlying problem;
   1. Create test cases to cover the identified problem;
   1. Work out a solution to rectify the behavior and make the newly created test cases pass;
   1. Make a pull request and go through peer review;
   
   As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
   
   sdk send message thrown topic not exists Exception,when namesrv restart and  broker register topic unfinished
   
   - What is expected to see?
   
   - What did you see instead?
   
   3. Please tell us about your environment:
   
   4. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
   
   
   


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

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org.apache.org

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


[GitHub] [rocketmq] complone commented on issue #5322: improving SDK topic route availability, when namsrv restart

Posted by GitBox <gi...@apache.org>.
complone commented on issue #5322:
URL: https://github.com/apache/rocketmq/issues/5322#issuecomment-1279594753

   Can you give the relevant log error information?


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

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

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


[GitHub] [rocketmq] lizhanhui commented on issue #5322: improving SDK topic route availability, when namsrv restart

Posted by GitBox <gi...@apache.org>.
lizhanhui commented on issue #5322:
URL: https://github.com/apache/rocketmq/issues/5322#issuecomment-1280375299

   Close as its PR is merged.


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

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

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


[GitHub] [rocketmq] complone commented on issue #5322: improving SDK topic route availability, when namsrv restart

Posted by GitBox <gi...@apache.org>.
complone commented on issue #5322:
URL: https://github.com/apache/rocketmq/issues/5322#issuecomment-1279908055

   > > Can you give the relevant log error information?
   > 
   > you can get TOPIC_NOT_EXIST response code and error msg is:No topic route info in name server for the topic
   
   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.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

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


[GitHub] [rocketmq] fuyou001 commented on issue #5322: improving SDK topic route availability, when namsrv restart

Posted by GitBox <gi...@apache.org>.
fuyou001 commented on issue #5322:
URL: https://github.com/apache/rocketmq/issues/5322#issuecomment-1279643423

   > Can you give the relevant log error information?
   
   you can get TOPIC_NOT_EXIST response code and error msg is:No topic route info in name server for the topic


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

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

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


[GitHub] [rocketmq] lizhanhui closed issue #5322: improving SDK topic route availability, when namsrv restart

Posted by GitBox <gi...@apache.org>.
lizhanhui closed issue #5322: improving SDK topic route availability, when namsrv  restart
URL: https://github.com/apache/rocketmq/issues/5322


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

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

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