[IOTDB-1099] Optimize insertablets logic in cluster module

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Core/Cluster
• Labels: pull-request-available
• Assignee: Houliang Qi
• Reporter: Xinyu Tan
• Created: 04/Jan/21 11:52
• Updated: 20/Feb/21 03:54
• Resolved: 21/Jan/21 02:10

Description

Currently, cluster module will process insertablets rpc by spliting it to multiple insertablet statements one by one, and each of them will take up a raft log, which need to complete the RaftLogManager's lock and be replicated to followers in one raft log.

In some user cases, a inserttablets will have 160 tablets, so this single client insertablets rpc will take up 160 raft logs containing insertabletPlan to replicate, which maybe optimized to one raft log containing insertabletsPlan if these devices all belong to same data group;

Therefore, we can process one insertablets rpc by grouping them to several raft logs containing insertabletsPlan according to their belonged data groups, just like the createMultiTimeSeriesPlan in current implementation.

Issue Links

• is a child of: IOTDB-68 IoTDB supports distributed version
• relates to: IOTDB-1163 Optimize the insertion speed of insertRecords interface in Session
• links to: GitHub Pull Request #2454