-
Bug
-
Resolution: Done
-
Major
-
0.8.0.Beta1
-
None
An exception (see DBZ-768) had been raised during a snapshot. The global read lock persisted indefinitely after the exception was raised; the global read lock wasn't released after the exception was raised nor was the global read lock timed out. The lock had to be released by force, by killing connect.