[MCOL-1074] Consider module consolidation Created: 2017-12-04  Updated: 2020-11-04  Resolved: 2020-11-04

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: None
Fix Version/s: 5.5.1

Type: New Feature Priority: Major
Reporter: Andrew Hutchings (Inactive) Assignee: Todd Stoffel (Inactive)
Resolution: Won't Do Votes: 0
Labels: Modernization

Epic Link: ColumnStore Installation Improvements

 Description   

At the moment we have the following processes in the UM:

  • DMLProc - Sends DML requests to WriteEngine
  • DDLProc - Processes DDL and sends to WriteEngine
  • ExeMgr - Processes SELECT queries, consolidates results
  • mysqld - The MariaDB Server

These can all be consolidated into the storage engine plugin for mysqld (apart from mysqld itself) which has the added benefit of reducing the network RTT for queries.

In the PM we have:

  • WriteEngine - Write engine processor
  • PrimProc - Primitive jobs processor
  • DecomSvr - Legacy decryption (InfiniDB < 4.0)
  • controllernode - The DBRM server (controls the extent map and UNDO logs)
  • workernode - A DBRM worker node (applies the extent map and UNDO log changes)

DecomSvr is a legacy process that is no longer required. This can be removed completely. The others can be consolidated into a single process. This is not such a high priority as getting the UM processes combined.

ProcMon/ProcMgr can remain independent until the replacement plan is executed.


Generated at Thu Feb 08 02:25:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.