featurebase/http
Seebs 7811d016b7 don't reuse sync.Mutex between translate readers
The functional option and returned closure combine to result in
us using the same sync.Mutex object for every TranslateReader on
a given server, which means that if one of them isn't producing anything,
we eventually end up waiting on that with all the others blocked
waiting for the lock. Use separate locks for each, of the same
type as the one initially provided as a template. This does mean
that multiple readers can be operating at once, but in theory
no two readers should ever be writing to the same stores, we
think.
2021-09-15 09:53:54 -05:00
..
client.go backport 1687 2021-09-09 10:11:51 -05:00
client_test.go Add test to reproduce deadlock 2020-10-12 12:32:58 -06:00
error.go Fix linter issues: vet 2018-07-19 11:37:50 -05:00
handler.go backport 1687 2021-09-09 10:11:51 -05:00
handler_internal_test.go Revert "back out the pql.Decimal changes" 2020-04-01 17:46:46 -05:00
handler_test.go fix lint 2020-04-22 14:30:14 -05:00
translator.go don't reuse sync.Mutex between translate readers 2021-09-15 09:53:54 -05:00
translator_test.go testhook: leak auditing infrastructure 2020-08-24 11:26:39 -05:00