Skip to main content

Singlestore multi node architecture components

 Singlestore multi node architecture components: 

Cluster: Cluster contains aggregator nodes and leaf nodes. Cluster is made of all nodes on which Singlestore DB is installed. 
Master Aggregator: Cluster contains one master aggregator, aggregator responsible for cluster monitoring and  failover. Master aggregator process DDL, DML, Failover, Reference Tables, CML
Child Aggregator: Cluster may have zero or more child aggregator, all it depends on query volume. The child aggregator process DML, and help master aggregator to reduce the load. 
Leaf: Cluster could have many leaves. The leaf node stores subset of data set. It could be a part of availability group when high availability is configured. 
Availability Group: It is a group of leaves - leaf nodes, stores redundant data. The purpose of availability group is to deliver high availability in case of leaf node failure. Redundancy is configurable via redundancy level. 
Master Partition: Data partition stored primarily on leaf node. 
Slave Partition: Copy of data partition from another node for high availability. 
Shard Key: Consists of 1 or 2 column of the tables. Singlestore store common shard key in same partition and node. i.e. if two tables have same shard key value these rows will be stored in a same partition on same node. 
Segment file: Columnstore data file, it is compressed. Each column of the table has its own file. Each file store 1M rows.
Sort key: Sort key is used for columnstore tables. It is clustered columnstore index.

Ref.: 

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more

MySQL slave Error_code: 1032 | MySQL slave drift | HA_ERR_KEY_NOT_FOUND

MySQL slave Error_code: 1032 | MySQL slave drift: With several MySQL, instance with master slave replication, I have one analytics MySQL, environment which is larger in terabytes, compared to other MySQL instances in the environment. Other MySQL instances with terabytes of data are running fine master, slave replication. But this analytics environment get started generating slave Error_code :1032. mysql> show slave status; Near relay log: Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_log_pos 5255306 Near master section: Could not execute Update_rows event on table <db_name>.<table_name>; Can't find record in '<table_name>', Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_l...
2 comments
Read more