fix(span-buffer): Fix crashing behavior in flusher

[untitaker]

• fix(span-buffer): Report exceptions from subprocess
• fix(span-buffer): Restart flusher properly

[codecov]

Codecov Report

Attention: Patch coverage is 55.55556% with 4 lines in your changes missing coverage. Please review.

⚠️ Parser warning

The parser emitted a warning. Please review your JUnit XML file:

Warning while parsing testcase attributes: Limit of string is 1000 chars, for name, we got 2083 at 1:157236 in /home/runner/work/sentry/sentry/.artifacts/pytest.junit.xml

Files with missing lines	Patch %	Lines
src/sentry/spans/consumers/process/flusher.py	55.55%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #91949      +/-   ##
==========================================
+ Coverage   86.51%   87.62%   +1.10%     
==========================================
  Files       10355    10356       +1     
  Lines      587271   587372     +101     
  Branches    22586    22586              
==========================================
+ Hits       508082   514667    +6585     
+ Misses      78762    72278    -6484     
  Partials      427      427              

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ KafkaException: KafkaError{code=MSG_SIZE_TOO_LARGE,val=10,str="Unable to produce message: Broker: Message size too large"} sentry.spans.consumers.process.flusher in produce View Issue
• ‼️ ConnectionError: Connection closed by server. sentry.spans.buffer in flush_segments View Issue
• ‼️ ClusterError: Command # 49 (SMEMBERS b'span-buf:s:{4509370939867136:3b8d3980493a4f6b9390fc59b52788ec}:997ebadc3a0ce43e') of pipeline caused error: TTL exhausted. sentry.spans.buffer in flush_segments View Issue
• ‼️ AskError: 12999 192.168.208.83:11054 sentry.spans.buffer in done_flush_segments View Issue
• ‼️ TimeoutError: Timeout connecting to server sentry.spans.buffer in done_flush_segments View Issue

_{Did you find this useful? React with a 👍 or 👎}