[MCOL-4507] Architecture document Created: 2021-01-20  Updated: 2021-07-01  Resolved: 2021-07-01

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

Type: Task Priority: Critical
Reporter: Timofey Turenko Assignee: Geoff Montee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MXS-2193 test Columnstore nodes created by MDBCI Closed

 Description   

Current multinode configuration guide does not give understanding about genera setup architecture (https://mariadb.com/docs/deploy/enterprise-multi-columnstore/)

Can architecture picture be drawn somewhere?

What is the server? what is the client? how does different system services interact between each other?

Documents says:

sudo systemctl restart mariadb
 
sudo systemctl restart mariadb-columnstore
 
sudo systemctl restart mariadb-columnstore-cmapi

We start 3 services, we need to configure shared storage for metadata, we need shared storage for data, we load the columnstore plugin, but there is no understanding of how do all components interact



 Comments   
Comment by Jacob Moorman (Inactive) [ 2021-01-20 ]

As noted in our call:

  • Documentation Team is preparing architectural documentation now, but if you need something sooner you should go to Todd and/or traiing materials.
Comment by Jacob Moorman (Inactive) [ 2021-04-23 ]

Still targeted for April closeout.

On Fri, Apr 23, 2021 at 10:31 AM Julien Fritsch (Jira) <jira@mariadb.org>

–
Jacob Moorman | m: +1-207-440-3690
Sr. Director of Documentation, MariaDB

Comment by Jacob Moorman (Inactive) [ 2021-05-10 ]

Technical review was completed, and content is pending final prep for
launch.

On Mon, May 10, 2021 at 2:04 AM Julien Fritsch (Jira) <jira@mariadb.org>

–
Jacob Moorman | m: +1-207-440-3690
Sr. Director of Documentation, MariaDB

Comment by Jacob Moorman (Inactive) [ 2021-07-01 ]

Shipped, https://mariadb.com/docs/multi-node/columnstore/architecture/#columnstore-architecture

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