Inspect the Current Configuration

{{ocient}} includes a variety of configuration settings that control how the system behaves the vast majority of these won't change in a typical deployment however, there is a small set more commonly changed to adjust for different workloads, hardware, and operating requirements configuration is primarily done through ddl or dcl and can be inspected using the docid\ pw7thsccelcw88z52wmkr you can contact ocient support to change configuration settings that apply across the entire system or to a subset of nodes each ocient node reads configuration settings during startup therefore, configuration changes require restarts for the new values to take effect for details, contact ocient support inspecting system configuration administrators typically need to know the effective configuration of the system and what has been overridden configuration overrides — a list of the overrides applied by administrators effective configuration — the complete list of all configuration parameters and their current values on each node viewing configuration overrides a system catalog table is provided that lists all ddl configuration overrides that are applied to the ocient system this table includes the configuration target type as well as the scope to which it is applied in the event that the scope is not system (see advanced configuration for cluster and node scopes), the scope id will indicate the cluster id or node id to which the configuration override applies example the following query retrieves all config overrides applied on the system and provides a friendly node name or cluster name where an override is limited in scope select cfg scope type, n name as node name, c name as cluster name, cfg key, cfg value from sys config cfg left join sys nodes n on n id = cfg scope id and cfg scope type = 'node' left join sys clusters c on c id = cfg scope id and cfg scope type = 'cluster'; output scope type node name cluster name key value \ node sales lts8 null lts memory warningheapmemoryusageratio 0 93999999999999995 system null null lts blobstoreparameters coremask 0b10000000000000000000 cluster null storagecluster1 lssparameters nvmeparameters useopal true node sales lts8 null lts lssparameters nvmeparameters iocoremask 68719542272 system null null sql pdfreservedmem 137438953472 viewing effective configuration using system table a system catalog table is provided that lists the effective configuration of each node example the following query retrieves the effective overrides for the sql role on the specified node select n name, nc key, nc value from sys node config nc join sys nodes n on nc node id = n id where n name = 'sql0' and key like 'sql%'; output name key value \ sql0 sql blobstoreparameters regionallocationunit 17179869184 sql0 sql blobstoreparameters pageutilizationexpand 0 75 sql0 sql blobstoreparameters pageutilizationcontract 0 25 sql0 sql blobstoreparameters maxfilesize 0 sql0 sql blobstoreparameters minfilesize 128mib sql0 sql blobstoreparameters blobpagesize 128kib sql0 sql blobstoreparameters stripewidth 0 sql0 sql blobstoreparameters coremask 0b10000000 sql0 sql cacheminfreememorypercent 0 109999999 sql0 sql cacheminsize 4096 sql0 sql cacheminkeeptime 720 sql0 sql purgecachefrequency 300 sql0 sql pdfreservedmem 0 sql0 sql numlevels 3 sql0 sql maxshutdownwaittime 1800000 sql0 sql shortquerymillis 1 sql0 sql timelimit 1800000 sql0 sql forcenetworkedvirtualtables false sql0 sql cachelimit 17179869184 sql0 sql optimizer tktoptimizer sql0 sql generator tktplangenerator sql0 sql validator tktvalidator sql0 sql concurrencytarget 5 viewing effective configuration using rest endpoints administrators can also view the effective system configuration using the config endpoint, a rest interface available on each node this endpoint shows every configuration parameter for the node and its current value it reflects the active values and might not reflect configuration overrides applied since the last node restart the config endpoint is found on each node at http //\<node hostname or ip address> 9090/v1/config and it returns a json representation of the active system configuration of the targeted node example curl http //10 0 1 7 9090/v1/config example response { "silotype" "xg runtime physicalsiloset t", "tlbfsinfo enabled" "true", "gdsclientparameters t batchtimer" "150000000n", "gdsclientparameters t maxbatchcount" "4096" "operatorvm vmsilomask" "0x3", "operatorvm vmparameters levels" "0x4", "operatorvm vmparameters statscachesize" "4gib", "operatorvm vmprotocolparameters routerpollrate" "250000000n", "operatorvm vmprotocolparameters buffereddatablocktimeout" "120000000000n" "lts ioopparameters bufferpool backingslabsize" "2mib", "lts ioopparameters bufferpool bufferpools\[0] pool size" "4kib", "lts ioopparameters bufferpool bufferpools\[0] pool count" "98304", "lts ioopparameters lbacachesize" "64", "lts targetfillratio" "1", "lts pdfreservedmem" "4gib" } related links https //docs ocient com/system catalog