featurebase/http
Seebs 76e4181740 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-03-08 17:04:52 -06:00
..
client.go Comment Status function 2021-03-03 23:47:47 +01:00
client_test.go Merge branch 'master' into disco 2021-03-02 22:11:04 -06:00
error.go Fix linter issues: vet 2018-07-19 11:37:50 -05:00
handler.go remove remaining references to "coordinator" 2021-02-23 17:23:09 -06:00
handler_internal_test.go Revert "back out the pql.Decimal changes" 2020-04-01 17:46:46 -05:00
handler_test.go remove port_mapper because it can't work with our unrestartable server 2021-02-24 11:25:46 -06:00
translator.go don't reuse sync.Mutex between translate readers 2021-03-08 17:04:52 -06:00
translator_test.go testhook: leak auditing infrastructure 2020-08-24 11:26:39 -05:00