Segmentation Fault (SIGSEGV) when cluster is enabled

[mgreen-sm]

Using version 1.6.2 (spec. prometheus-gravel-gateway_v1.6.2_x86_64-unknown-linux-musl), I've noticed that when the cluster is enabled, a segmentation fault causes it to crash when writing a metric.

GDB shows it as:

0x00007fb8f0195ab9 in parking_lot::condvar::Condvar::wait_until_internal ()
0x00007fb8f017d0ae in _ZN5tokio4park6thread5Inner4park17h6473e14d105f4ff5E.llvm.5059386539350869202 ()
0x00007fb8f017d44b in <tokio::park::thread::CachedParkThread as tokio::park::Park>::park ()
0x00007fb8efe4f655 in tokio::park::thread::CachedParkThread::block_on ()

Thread 2 "tokio-runtime-w" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 11614]
0x0000000000000000 in ?? ()

It was simple enough to reproduce using:

gravel-gateway --cluster-enabled -l localhost:4280 --peer localhost:4281 --peer localhost:4282
gravel-gateway --cluster-enabled -l localhost:4281 --peer localhost:4280 --peer localhost:4282
gravel-gateway --cluster-enabled -l localhost:4282 --peer localhost:4281 --peer localhost:4280

echo 'gravel_test_value_4{clearmode="aggregate"} 1' | curl -Lvv --data-binary @- localhost:4281/metrics
*   Trying 127.0.0.1:4281...
* Connected to localhost (127.0.0.1) port 4281 (#0)
> POST /metrics HTTP/1.1
> Host: localhost:4281
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Length: 45
> Content-Type: application/x-www-form-urlencoded
> 
* Empty reply from server
* Closing connection 0