[GitHub] [pulsar-client-go] jinfengnarvar commented on issue #239: panic during rapid send of many large-sized payloads: "panic: send on closed channel"

[GitBox <gi...@apache.org>]

jinfengnarvar commented on issue #239:
URL: https://github.com/apache/pulsar-client-go/issues/239#issuecomment-624640208


   @wolfstudy thx. i'm also trying to find a (more) deterministic way to repro it - right now it only occurs in our prod env service that processes multiple large files at the same time. crash occurs frequently but not in a deterministic way.
   
   also i'm wondering if anyone has any insight of what's the repeated blocks of "failed to write...; connection closed...; reconnecting to broker....;" failure logs indicate? Apparently these logs are from within the pulsar go client, you guys happen to use `github.com/sirupsen/logrus` as well so we were able to catch it and dump it out.
   
   my question is we're in the midst of writing to producer partitions, and what could usually cause the connection sever? broker overloaded (due to volume or payload size?) Anything on the pulsar server side can be configured to reveal the connection drop failure reason?


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