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 2022/09/21 11:50:09 UTC

[GitHub] [pulsar-client-go] frankjkelly opened a new issue, #851: Support backoff parameters as optional parameters

frankjkelly opened a new issue, #851:
URL: https://github.com/apache/pulsar-client-go/issues/851

   **Is your feature request related to a problem? Please describe.**
   
   The default backoff parameters are alternatively very aggressive (100ms minimum) and not aggressive enough (60 seconds maximum) for high throughput / short response time environments where we are trying to
   * Avoid a "thundering herd" / "retry storm" (increase the minimum backoff)
   * But need to fail fast (lower the maximum backoff) 
   
   **Describe the solution you'd like**
   
   Make these settings parameterizable
   https://github.com/apache/pulsar-client-go/blob/bd19458b32ff89206c135cc647336e690e99c32f/pulsar/internal/backoff.go#L36-L38
   
   **Describe alternatives you've considered**
   None I can think of 
   
   **Additional context**
   Add any other context or screenshots about the feature request here.
   


-- 
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: commits-unsubscribe@pulsar.apache.org.apache.org

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

[GitHub] [pulsar-client-go] wolfstudy commented on issue #851: Support backoff parameters as optional parameters

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

   > 
   
   Thanks @frankjkelly feedback, I think this is a very rational requirement, we can implement this function by combining these configuration parameters


-- 
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: commits-unsubscribe@pulsar.apache.org

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

[GitHub] [pulsar-client-go] codelipenghui closed issue #851: Support backoff parameters as optional parameters

Posted by GitBox <gi...@apache.org>.
codelipenghui closed issue #851: Support backoff parameters as optional parameters
URL: https://github.com/apache/pulsar-client-go/issues/851


-- 
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: commits-unsubscribe@pulsar.apache.org

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

[GitHub] [pulsar-client-go] wolfstudy commented on issue #851: Support backoff parameters as optional parameters

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

   Thanks @frankjkelly feedback, I think this is a very rational requirement, we can implement this function by combining these configuration parameters


-- 
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: commits-unsubscribe@pulsar.apache.org

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