4 Operator

 • 

1.2K Posts

June 11th, 2014 09:00

No persistant harm, and fixed in 7.0.2.9 and 7.1.0.3

from the 7.0 MR  and 7.1 MR release notes:

During read operations, locks were sometimes acquired out of order, preventing other necessary locks from being acquired. When locks were acquired out of order, the operation was immediately restarted and the necessary locks were successfully acquired, however, DSR failures similar to the following were logged for the initial failure:

write failed: ENEEDLOCK 

No Events found!

Top