Server does not cascade shutdown or recover when SQL workers crash
SOF3 opened this issue · 3 comments
Describe the bug
A clear and concise description of what the bug is.
I accidentally changed the type of $queries for executeSelectRaw from list<string> to array{list<string>}. The query was serialized and unserialized in the worker send queue as-is, and only caused a crash when actually running in MysqliThread::executeQuery. This only crashes the worker thread, but the server keeps on running. If this happens in production scenario, all SQL workers will get stuck and all queries will end up taking forever to run, and server admin has no way to know what's wrong except by reading the crash output on the stdout, which does not even get sent to the PocketMine logger.
Environment
hub.docker.com/pmmp/pocketmine-mp:4.0.2
OS: Ubuntu
PocketMine version: 4.0.2
If you're using Worker it won't actually crash, it'll just bork the task involved. pmmp/ext-pmmpthread#34
It isn't a worker. Just a thread on a wait loop.
Don't ask me why I didn't use a Worker.
This will be fixed by the release of pmmpthread 6.0.0 (pmmp/ext-pmmpthread@5c595c1)