Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
2.4.1
-
None
-
Reviewed
Description
During upgrade of an HA cluster, the JournalNode attempts to rename the current storage directory to previous. However, the process still holds the last committed transaction ID file opened while this is happening. On Windows, this is a locking violation that causes the rename operation to fail. Ultimately the whole upgrade fails. There is a similar problem during rollback too.