mirror of
https://github.com/prometheus/prometheus.git
synced 2025-01-26 05:01:23 -08:00
bfb1500a38
If a queue is stopped and one of its shards happens to hit the batch_send_deadline at the same time a deadlock can occur where stop holds the mutex and will not release it until the send is finished, but the send needs the mutex to retrieve the most recent batch. This is fixed by using a second mutex just for writing. In addition, the test I wrote exposed a case where during shutdown a batch could be sent twice due to concurrent calls to queue.Batch() and queue.FlushAndShutdown(). Protect these with a mutex as well. Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com> |
||
|---|---|---|
| .. | ||
| chunked.go | ||
| chunked_test.go | ||
| client.go | ||
| client_test.go | ||
| codec.go | ||
| codec_test.go | ||
| ewma.go | ||
| intern.go | ||
| intern_test.go | ||
| max_timestamp.go | ||
| metadata_watcher.go | ||
| metadata_watcher_test.go | ||
| queue_manager.go | ||
| queue_manager_test.go | ||
| read.go | ||
| read_handler.go | ||
| read_handler_test.go | ||
| read_test.go | ||
| storage.go | ||
| storage_test.go | ||
| write.go | ||
| write_handler.go | ||
| write_handler_test.go | ||
| write_test.go | ||