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/07/21 03:10:17 UTC

[GitHub] [pulsar-client-go] yarthur1 opened a new issue #327: the problem of partition producer number 

yarthur1 opened a new issue #327:
URL: https://github.com/apache/pulsar-client-go/issues/327


   #### Expected behavior
   
   After a bundle successfully moved from broker A to broker B , goclient log show that partition producer has reconnected new broker, but goclient has lots of warn log like"level=warning msg="Got unexpected send receipt for message: ledgerId:87806 entryId:10433 "...". Grafana dashboard show the number of producer have some change,and eventually is not correct
   
   broker log
   broker A unload bundle
   ![image](https://user-images.githubusercontent.com/30923528/88007314-52758380-cb40-11ea-9829-d100be04dac4.png)
   
   ![image](https://user-images.githubusercontent.com/30923528/88007212-088c9d80-cb40-11ea-8086-100cefa1a439.png)
   
   broker B load bundle
   ![image](https://user-images.githubusercontent.com/30923528/88007513-b7c97480-cb40-11ea-9180-faf4898d85c6.png)
   
   ![image](https://user-images.githubusercontent.com/30923528/88007442-923c6b00-cb40-11ea-84f8-832de9f428f1.png)
   
   Go client log
   ![image](https://user-images.githubusercontent.com/30923528/88007978-bc425d00-cb41-11ea-9163-2bc02dda1932.png)
   ![image](https://user-images.githubusercontent.com/30923528/88007996-c9f7e280-cb41-11ea-8ad5-82ce0f7d2011.png)
   
   grafana 
   ![image](https://user-images.githubusercontent.com/30923528/88008335-a5503a80-cb42-11ea-900e-9832aa004338.png)
   
   #### System configuration
   Pulsar version: 2.6.0
   Go client version: 0.1.0
   


----------------------------------------------------------------
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-client-go] LvBay edited a comment on issue #327: the problem of partition producer number

Posted by GitBox <gi...@apache.org>.
LvBay edited a comment on issue #327:
URL: https://github.com/apache/pulsar-client-go/issues/327#issuecomment-663320840


   @yarthur1 Did you use the same client instance to create both  consumers and a producers?
   I have encountered a similar problem and have submitted a [PR](https://github.com/apache/pulsar-client-go/pull/326#pullrequestreview-454602379) to fix it, hope it can help you.


----------------------------------------------------------------
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-client-go] LvBay commented on issue #327: the problem of partition producer number

Posted by GitBox <gi...@apache.org>.
LvBay commented on issue #327:
URL: https://github.com/apache/pulsar-client-go/issues/327#issuecomment-663320840


   @yarthur1 Did you use the same client instance to create both  consumers and a producers?
   I have encountered a similar problem and have submitted a PR to fix it, hope it can help you.


----------------------------------------------------------------
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-client-go] sijie commented on issue #327: the problem of partition producer number

Posted by GitBox <gi...@apache.org>.
sijie commented on issue #327:
URL: https://github.com/apache/pulsar-client-go/issues/327#issuecomment-662189447


   @yarthur1 I don't think it is a problem on either client or broker side. This sounds like a grafana problem. Have you checked the query to understand if it is a metric problem?


----------------------------------------------------------------
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-client-go] yarthur1 commented on issue #327: the problem of partition producer number

Posted by GitBox <gi...@apache.org>.
yarthur1 commented on issue #327:
URL: https://github.com/apache/pulsar-client-go/issues/327#issuecomment-663327042


   > @yarthur1 Did you use the same client instance to create both consumers and a producers?
   > I have encountered a similar problem and have submitted a [PR](https://github.com/apache/pulsar-client-go/pull/326#pullrequestreview-454602379) to fix it, hope it can help you.
   
   yes,I  use the same client instance. thanks,I will view it
   


----------------------------------------------------------------
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-client-go] yarthur1 commented on issue #327: the problem of partition producer number

Posted by GitBox <gi...@apache.org>.
yarthur1 commented on issue #327:
URL: https://github.com/apache/pulsar-client-go/issues/327#issuecomment-662222239


   > @yarthur1 I don't think it is a problem on either client or broker side. This sounds like a grafana problem. Have you checked the query to understand if it is a metric problem?
   
   But it lead to send rate slow, I have add timeout check on Go client send method to test and find lots of timeout


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