Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
-
None
Description
When there's an error on lookup or construction of an execution plan, the lock is accidentally held causing the worker to freeze.
Shouldn't be user affecting, as most plans and lookups are correct without error, but if there's a transient GRPC issue on lookup, that might cause an otherwise healthy worker to deadlock.