[IOTDB-1529] MLog Recover and StorageGroup atomic set

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: master branch, 0.12.2-SNAPSHOT
• Component/s: Core/Server
• Labels: metadata pull-request-available
• Assignee: Unassigned
• Reporter: Yukun Zhou
• Created: 27/Jul/21 08:43
• Updated: 27/Jul/21 12:02
• Resolved: 27/Jul/21 12:02

Description

MLog Recover bug

The index of mlog after MManager.applyMLog is not correct. Once the plan has been read successfully but executed unsuccessfully, the index should increase.

 

StorageGroup atomic set

The add storageGroupMNode in mtree.setStorageGroup is not atomic, which will result in multi same record in mlog and the subtree may be dropped.

Issue Links

• links to: GitHub Pull Request #3635
• links to: GitHub Pull Request #3636