Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Deploying SingleStore Database on Dell PowerFlex 3.6
Introduction Product overview
Product overview
PowerFlex overview
PowerFlex delivers transformational value
PowerFlex software components
PowerFlex consumption options
Flexible consumption-based billing options
SingleStore overview
SingleStore cluster components
VMware vSphere overview
vSphere 7
Solution architecture SingleStore cluster deployment on PowerFlex Testing and validation Conclusion Appendix Best practices References

SingleStore cluster components

SingleStore cluster components

  • A SingleStore cluster consists of the following components:

    Leaf

    A leaf is a node that stores a subset of a cluster’s data. It functions as a storage and compute node. To optimize performance, SingleStore automatically distributes data across leaf nodes into partitions. Each leaf contains several partitions. A cluster contains many leaves and each leaf is in one of the Leaf States.

    Aggregator

    An aggregator is a node that routes queries to the leaves, aggregates intermediate results, and sends the results back to the client. There are two types of aggregators: master and child. 

    A master aggregator is a specialized aggregator responsible for cluster monitoring and failover. It orchestrates the basic cluster operations and all data definition language (DDL) operations. For more information, see Aggregator set as master.

    A cluster contains exactly one master aggregator. A cluster may contain zero or more child aggregators (depending on the query volume).

    Partition

    A partition contains a subset (a shard) of data in a database. Each partition holds a vertical slice of data, which is distributed as per a hashing algorithm on the primary key or randomly for keyless sharded databases. A leaf node contains multiple partitions. When you run the CREATE DATABASE syntax, SingleStore splits the database into partitions that are distributed evenly among available leaf nodes. You can use the CREATE DATABASE syntax to add the number of partitions with the PARTITIONS=X option.

    If you do not add the number of partitions explicitly, the default value is used (the number of leaf nodes x the value of the default_partitions_per_leafengine variable).

    Tables

    SingleStore stores data in the following types of tables:

    • Universal Storage: This is the default type of table used in SingleStore database. Universal storage tables support large-scale Online Transaction Processing (OLTP) and Hybrid Transactional and Analytical Processing (HTAP) workloads at a lower total cost of ownership (TCO). Universal Storage table is a continuous evolution of the columnstore tables and supports transactional workloads that would have traditionally used the rowstore tables. SingleStore recommends using the Universal Storage tables for all kinds of workloads.
    • Columnstore: SingleStore database stores columnstore tables on disk with each column as a unit and stores the segments of data for each column together in the same physical location. When you run a query referencing a few columns in a table, it will scan the columns that are stated in the query. Another important benefit of columnstore table is that they can be compressed.
    • Rowstore: In a rowstore table, each row acts as a unit and stores all fields for a given row together in the same physical location. In-memory rowstore tables are used for high-performance OLTP workloads.

    The data can be stored in the SingleStore tables in the following ways:

    • Sharded or Reference – Data in a sharded table is distributed across partitions whereas, in a reference table data is fully replicated to all nodes in a cluster.
    • Persisted or Temporary - Defines whether the data that is stored in a table is persisted or stored temporarily during a client session. Temporary tables can further be classified into regular temporary tables and global temporary tables.