Open dlidstrom opened 2 months ago
I see the same error and for me it appears to be related to the —enable-compression
flag. If I set that I get the same error. If I don’t enable that then everything is fine.
This error was introduced via https://github.com/bojand/ghz/pull/444, where a map is updated by many workers without a mutex.
Proto file(s)
Not sure I can share these.
Command line arguments / config
Describe the bug
ghz fails after less then a minute.
Environment
Windows Server 2019
Output