Liberxue opened a new issue #555: Best Practice For NameServer - HTTP Endpoint
URL: https://github.com/apache/rocketmq/issues/555
 
 
   The issue tracker is **ONLY** used for bug report and feature request. Keep 
in mind, please check whether there is an existing same report before your 
raise a new one.
   
   Alternately (especially if your communication is not a bug report), you can 
send mail to our [mailing lists](http://rocketmq.apache.org/about/contact/). We 
welcome any friendly suggestions, bug fixes, collaboration and other 
improvements.
   
   Please ensure that your bug report is clear and that it is complete. 
Otherwise, we may be unable to understand it or to reproduce it, either of 
which would prevent us from fixing the bug. We strongly recommend the 
report(bug report or feature request) could include some hints as the following:
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
   
   
![image](https://user-images.githubusercontent.com/5831248/48822573-8101f080-ed98-11e8-8f71-0247ed3a329d.png)
   
   - What did you expect to see?
   https://rocketmq.apache.org/docs/best-practice-namesvr/
   - What did you see instead?
   
   2. Please tell us about your environment:
   ```
   Request Method: GET
   Request URL:  http://127.0.0.1:8080/rocketmq/nsaddr  
   Response: 
   127.0.0.1:9876;127.0.0.1:9876
   ```
   
![image](https://user-images.githubusercontent.com/5831248/48822917-c1ae3980-ed99-11e8-9940-0fa070ee4207.png)
   
   3. Other information (e.g. detailed explanation, logs, related issues, 
suggestions how to fix, etc):
   
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   
   ```
   2018-11-21 13:52:28 INFO ShutdownHook - shutdown thread 
PullRequestHoldService interrupt false
   2018-11-21 13:52:28 INFO PullRequestHoldService - PullRequestHoldService 
service end
   2018-11-21 13:52:28 INFO ShutdownHook - join thread PullRequestHoldService 
eclipse time(ms) 0 90000
   2018-11-21 13:52:31 INFO BrokerControllerScheduledThread1 - dispatch behind 
commit log 0 bytes
   2018-11-21 13:52:31 INFO BrokerControllerScheduledThread1 - Slave fall 
behind master: 675410 bytes
   2018-11-21 13:52:39 INFO main - 
rocketmqHome=/Users/liberxue/SourceRead/rocketmq//distribution
   2018-11-21 13:52:39 INFO main - namesrvAddr=
   2018-11-21 13:52:39 INFO main - brokerIP1=192.168.187.154
   2018-11-21 13:52:39 INFO main - brokerIP2=192.168.187.154
   2018-11-21 13:52:39 INFO main - brokerName=liberxuedeMacBook-Pro.local
   2018-11-21 13:52:39 INFO main - brokerClusterName=DefaultCluster
   ....
   
   2018-11-21 13:52:39 INFO main - transientStorePoolSize=5
   2018-11-21 13:52:39 INFO main - fastFailIfNoBufferInStorePool=false
   2018-11-21 13:52:39 INFO main - http://127.0.0.1:8080/rocketmq/nsaddr
   2018-11-21 13:52:39 INFO main - null
   2018-11-21 13:52:40 INFO main - load exist local topic, TopicConfig 
[topicName=localhost, readQueueNums=4, writeQueueNums=4, perm=RW-, 
topicFilterType=SINGLE_TAG, topicSysFlag=0, order=false]
   ```
   2. Provide any additional detail on your proposed use case for this feature.
   
   2. Indicate the importance of this issue to you (blocker, must-have, 
should-have, nice-to-have). Are you currently using any workarounds to address 
this issue?
   
   4. If there are some sub-tasks using -[] for each subtask and create a 
corresponding issue to map to the sub task:
   
   - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 
description here, 
   
![image](https://user-images.githubusercontent.com/5831248/48822573-8101f080-ed98-11e8-8f71-0247ed3a329d.png)
   
   - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 
description here,
   - ...
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to