Ocient Application Configuration

these steps assume that you have already completed the process for bootstrapping your {{ocient}} system nodes if you have not done this yet, perform the ocient system bootstrapping docid\ xszfsrrbjlndjdlsovc74 steps before beginning this configuration process now that the nodes have all completed bootstrapping, you must properly configure the nodes to perform their roles you should run these commands using a sql connection to one of the sql nodes in your system for details, see connect to ocient docid\ lb5x4qrnpht6m9v2evhuc the ocient application configuration process consists of these steps ocient application configuration docid\ lxwooha86u8vxntua3bp1 ocient application configuration docid\ lxwooha86u8vxntua3bp1 ocient application configuration docid\ lxwooha86u8vxntua3bp1 ocient application configuration docid\ lxwooha86u8vxntua3bp1 creating a storage space to create a storage space with 12 segments, use width=12 and parity width=2 two of these segments are the parity portion, and 10 of these segments are the data portion create storagespace teststoragespace width = 12, parity width = 2; the storage space name must begin with a letter followed by letters, numbers, and underscores you can view all storage spaces in the system by querying the sys storage spaces system catalog table select from sys storage spaces; for details about creating a storage space to suit your system needs, see configure storage spaces docid\ n cqwc cwil7x0sjsabcn creating storage clusters you must have at least one storage cluster to configure an ocient system a storage cluster is a set of foundation nodes with an associated storage space that coordinate to reliably store data and serve queries create a foundation cluster create cluster lts cluster type lts storagespace "teststoragespace" participants=('lts0','lts1','lts2','lts3','lts4','lts5','lts6','lts7','lts8','lts9','lts10','lts11'); loader nodes and sql nodes do not need to be placed into a cluster at a minimum, the number of participants must be the width specified in the storage space this number can be greater if you overprovision the system for details about storage spaces and related settings, overprovisioning, and parity, see core elements of an ocient system docid\ mw cl16ivsflmrdqgwtk6 view all clusters in the system select from sys clusters; v iew all clusters and their associated nodes select c name as cluster name, c cluster type, n name as node name from sys node clusters nc join sys clusters c on nc cluster id = c id join sys nodes n on nc node id = n id; you must restart all nodes with the sql role after adding a storage cluster assigning service roles assign service roles to each accepted node this process defines how each node participates in queries and the management of the system view all nodes and their configured roles select n name as node name, sr service role type from sys nodes n left join sys service roles sr on sr node id = n id; the addition of nodes to the storage cluster in the prior step automatically assigns lts to the foundation nodes that you included add the remaining sql , admin , and streamloader roles to the appropriate nodes alter node "sql1" add role sql; alter node "sql1" add role admin; alter node "loader1" add role streamloader; the admin role can operate standalone or on the same node as the sql role restart the nodes with roles assigned to the nodes, you can restart the rolehostd process on all nodes at a shell terminal on each node, run this command sudo systemctl restart rolehostd if any custom configuration settings are applied to running nodes during other configurations, be sure to restart the rolehostd process before proceeding you can check the status of nodes using the status endpoint on each node from a terminal assuming ip addresses 10 10 0 2 and 10 10 0 3 for sql1 and lts0 , respectively, you can check the status with these curl commands curl http //10 10 0 2 9090/v1/status curl http //10 10 0 3 9090/v1/status after all of the nodes are active , ocient is ready to use for queries creating an ocient system with multiple storage clusters if you need an ocient system that requires 10 or more foundation nodes in the storage cluster, then you can create multiple storage clusters for considerations to take into account when you work with multiple storage clusters, see multiple storage clusters for loading data docid\ hg8wacdzy s2zap9rio create a multiple storage cluster with 12 nodes create a storage space store with width 5 and parity width 1 using the create storagespace sql statement create storagespace store width = 5, parity width = 1; create multiple clusters using the create cluster sql statements using the storage space store split the foundation nodes among the clusters cluster 0 storage cluster has foundation nodes lts0 through lts5 , while cluster 1 has lts6 through lts11 create cluster cluster 0 type=lts participants=("lts0", "lts1", "lts2", "lts3", "lts4", "lts5") storagespace=store; create cluster cluster 1 type=lts participants=("lts6", "lts7", "lts8", "lts9", "lts10", "lts11") storagespace=store; validating the system after configuration after configuration, you can run a system check to validate the ocient installation and bootstrapping for details, see checking system after configuration docid\ d9ulo35ly51cnk4lzxjty next step follow the process in ingest data with legacy lat reference docid\ luijhab6vyj6g1gn5bhth to create a database and a table, then load data from a set of files located on a cloud object storage related links installation reference docid\ m5rhgylfwibyg0 9zrgni install an ocient system docid\ clmx7aipvis6ctybuagzx