Managing with gadmin

Search…
Managing TigerGraph Servers with gadmin
Introduction
TigerGraph Graph Administrator (gadmin) is a tool for managing TigerGraph servers. It has a self-contained help function and a man page, whose output is shown below for reference. If you are unfamiliar with the TigerGraph servers, please see GET STARTED with TigerGraph.​
To see a listing of all the options or commands available for gadmin, run any of the following commands:
1
$ gadmin -h
2
$ gadmin --help
Copied!
After changing a configuration setting, it is generally necessary to run **gadmin config apply. **Some commands invoke config apply automatically. If you are not certain, just run
gadmin config apply
List of commands
Below is the man page for gadmin. Most of the commands are self-explanatory. Common examples are provided with each command.
NOTE: Some commands have changed in v3.0. In particular,
gadmin set <config | license>
has changed to
gadmin <config | license> set
1
GADMIN(1)                         User Commands                                GADMIN(1)
2
​
3
NAME
4
       gadmin - manual page for TigerGraph Administrator.
5
​
6
SYNOPSIS
7
       gadmin [flags]
8
       gadmin [command]
9
​
10
DESCRIPTION
11
       gadmin is a tool for managing TigerGraph servers
12
​
13
OPTIONS
14
       Available Commands:
15
         autocomplete Generate autocomplete script
16
         config       Manage the configuration for the TigerGraph system
17
         help         Help about any command
18
         init         Init the whole cluster or given service
19
         license      Manage TigerGraph license
20
         log          List log files of the given services or all services
21
         reset        Reset the whole init or given service with its data
22
         restart      Restart services by service id
23
         start        Start services by service id
24
         status       Show current status of service
25
         stop         Stop services by service id
26
         version      Show the version information
27
​
28
Flags:
29
      --debug   enable debug log output to stdout
30
  -h, --help    help for gadmin
31
​
32
Use "gadmin [command] --help" for more information about a command.
33
GADMIN(1)
Copied!
gadmin autocomplete
Gadmin autocomplete is more of a feature than a command. It is an auto-complete feature that allows you to see all possible entries of a specific configuration. You can press tab when typing a command to either print out all possible entries, or auto-complete the entry you are currently typing.
1
$ gadmin autocomplete -h 
2
​
3
Generate autocomplete script
4
​
5
Usage:
6
  gadmin autocomplete <bash|zsh> [flags]
7
​
8
Description:
9
  If you want to make this automatic, add ". <(gadmin autocomplete bash)" to your
10
  .bashrc file.
11
​
12
Flags:
13
  -h, --help   help for autocomplete
14
​
15
Global Flags:
16
      --debug   enable debug log output to stdout
Copied!
The example below shows an example of the autocomplete for the command gadmin status.
1
[email protected]:~$ gadmin status
2
admin         exe           ifm           nginx
3
all           gpe           infra         restpp
4
ctrl          gse           kafka         ts3
5
dict          gsql          kafkaconn     ts3serv
6
etcd          gui           kafkastrm-ll  zk
Copied!
gadmin config
gadmin config commands are used to manage the configuration for the TigerGraph system. To get a complete list of configuration parameters that are available, see Configuration Parameters.
gadmin config has many sub-entries as well, they will be listed below.
1
$ gadmin config -h
2
​
3
Manage the configuration for the TigerGraph system
4
​
5
Usage:
6
  gadmin config [flags]
7
  gadmin config [command]
8
​
9
Description:
10
  You can specify local config file to turn on file mode, which no remote
11
  connection will be made and the configs are read/write from/to the file.Note: Not
12
  all config commands work on file mode.
13
​
14
Available Commands:
15
  apply       Apply the config changes in staging state
16
  diff        Show the differences between staging and applied configs
17
  discard     Discard the staging config changes
18
  dump        Dump the staging system config in json format
19
  entry       Configure the entries with given substring patterns interactively
20
  get         Get the config value of given entry name non-interactivly
21
  group       Configure the entries of given groups interactively
22
  init        Initialize configuration
23
  list        List the available config entries or groups
24
  reset       Reset the given entry to its default value
25
  set         Configure the entry of given config entry name in non-interactivly
26
​
27
Flags:
28
      --file string   specify config file path
29
  -h, --help          help for config
30
​
31
Global Flags:
32
      --debug   enable debug log output to stdout
33
​
Copied!
Example: Change the retention size of the kafka queue to 10GB:
1
$ gadmin config set Kafka.RetentionSizeGB 10
Copied!
gadmin config apply
1
$ gadmin config apply -h
2
Apply the config changes in staging state
3
​
4
Usage:
5
  gadmin config apply [flags]
6
​
7
Flags:
8
  -y, --confirm              confirm to apply
9
  -f, --force                force components to apply new config
10
  -h, --help                 help for apply
11
      --initial              config apply with the initial configuration when the remote config (ETCD) is empty
12
      --with-config string   the input config file used to config apply, will overwrite both local and remote(ETCD)
13
​
14
Global Flags:
15
      --debug         enable debug log output to stdout
16
      --file string   specify config file path
Copied!
gadmin config diff
Show what configuration changes were made.
1
$ gadmin config diff -h
2
Show the differences between staging and applied configs
3
​
4
Usage:
5
  gadmin config diff [flags]
6
​
7
Flags:
8
  -h, --help   help for diff
9
​
10
Global Flags:
11
      --debug         enable debug log output to stdout
12
      --file string   specify config file path
Copied!
gadmin config discard
Discard the configuration changes without applying them.
1
$ gadmin config discard -h
2
Discard the staging config changes
3
​
4
Usage:
5
  gadmin config discard [flags]
6
​
7
Flags:
8
  -h, --help   help for discard
9
​
10
Global Flags:
11
      --debug         enable debug log output to stdout
12
      --file string   specify config file path
Copied!
gadmin config dump
Display all configuration entries.
1
$ gadmin config dump -h
2
Dump the staging system config in json format
3
​
4
Usage:
5
  gadmin config dump [flags]
6
​
7
Flags:
8
  -h, --help   help for dump
9
​
10
Global Flags:
11
      --debug         enable debug log output to stdout
12
      --file string   specify config file path
Copied!
gadmin config entry
Change a configuration entry.
1
$ gadmin config entry -h
2
Configure the entries with given substring patterns interactively
3
​
4
Usage:
5
  gadmin config entry [EntryName] [flags]
6
​
7
Description:
8
  You may use `config entry system` to go through all the system related entries.
9
​
10
Flags:
11
  -a, --all     configure all entries
12
      --basic   configure basic entries only
13
  -h, --help    help for entry
14
​
15
Global Flags:
16
      --debug         enable debug log output to stdout
17
      --file string   specify config file path
Copied!
gadmin config get
Get the value of a specific configuration entry.
1
$ gadmin config get -h
2
Get the config value of given entry name non-interactivly
3
​
4
Usage:
5
  gadmin config get [EntryName] [flags]
6
​
7
Flags:
8
  -h, --help   help for get
9
​
10
Global Flags:
11
      --debug         enable debug log output to stdout
12
      --file string   specify config file path
Copied!
gadmin config group
Configure entries for a specific service group.
e.g. KAFKA, GPE, ZK
1
$ gadmin config group -h
2
Configure the entries of given groups interactively
3
​
4
Usage:
5
  gadmin config group [GroupName] [flags]
6
​
7
Description:
8
  You may use `gadmin config list group` to see all the groups.
9
​
10
Flags:
11
  -h, --help   help for group
12
​
13
Global Flags:
14
      --debug         enable debug log output to stdout
15
      --file string   specify config file path
Copied!
gadmin config init
Initialize your configuration.
1
$ gadmin config init -h
2
Initialize configuration
3
​
4
Usage:
5
  gadmin config init [flags]
6
​
7
Flags:
8
      --all            display every configurable entry
9
      --expert         display node assignment entries
10
      --ha             enable HA for init
11
  -h, --help           help for init
12
  -i, --input string   provide an input file name and init the configuration silently with the provided input file
13
      --template       show the template for init initialization
14
​
15
Global Flags:
16
      --debug         enable debug log output to stdout
17
      --file string   specify config file path
Copied!
gadmin config list
List all configurable entries or entry groups.
1
$ gadmin config list -h
2
List the available config entries or groups
3
​
4
Usage:
5
  gadmin config list <group|entry> [flags]
6
​
7
Description:
8
  List prints out the available config groups or config entries, which can be used
9
  in entry/group commands.
10
​
11
Flags:
12
      --basic   list basic entries only
13
  -h, --help    help for list
14
​
15
Global Flags:
16
      --debug         enable debug log output to stdout
17
      --file string   specify config file path
Copied!
gadmin config set
1
$ gadmin config set -h
2
Configure the entry of given config entry name in a non-interactive manner
3
​
4
Usage:
5
  gadmin config set [EntryName] [EntryValue] [flags]
6
​
7
Description:
8
  [EntryName] [EntryValue] must be provided in pairs, and use space to separate
9
  each pair.
10
​
11
Flags:
12
  -h, --help   help for set
13
​
14
Global Flags:
15
      --debug         enable debug log output to stdout
16
      --file string   specify config file path
Copied!
gadmin config reset
Reset one or more configuration parameters to their default setting. View the full list of configuration parameters and their default values at Configuration Parameters.
1
Usage:
2
gadmin config reset [EntryName...] [flags]
3
​
4
Flags:
5
-h, --help   help for reset
6
​
7
Global Flags:
8
--debug         enable debug log output to stdout
9
--file string   specify config file path
Copied!
gadmin init
1
$ gadmin init -h
2
​
3
Init the whole cluster or given service
4
​
5
Usage:
6
  gadmin init [flags]
7
  gadmin init [command]
8
​
9
Description:
10
  Init command initializes the cluster/kafka. When "cluster" is specified,
11
  a config path is required.
12
​
13
Available Commands:
14
  cluster     Init the whole cluster
15
  kafka       Init the KAFKA
16
​
17
Flags:
18
  -h, --help   help for init
19
​
20
Global Flags:
21
      --debug   enable debug log output to stdout
22
​
23
Use "gadmin init [command] --help" for more information about a command.
Copied!
gadmin license
Options for configuring your license.
1
$ gadmin license -h
2
​
3
Manage TigerGraph license
4
​
5
Usage:
6
  gadmin license [flags]
7
  gadmin license [command]
8
​
9
Available Commands:
10
  seed        Collects host signature and generates seed file for issuing license
11
  set         Set new license
12
  status      Display license status and info
13
​
14
Flags:
15
  -h, --help   help for license
16
​
17
Global Flags:
18
      --debug   enable debug log output to stdout
19
​
20
Use "gadmin license [command] --help" for more information about a command.
Copied!
Generating a license seed
To generate a license seed, use the following command:
1
$ gadmin license seed <host_signature_type>
2
# host_signature_type: [aws|azure|gcp|hardware|node-id]
Copied!
Depending on your host machine, you need to choose the appropriate host signature type. If you are generating the seed from a cloud instance, choose the corresponding cloud provider as your signature type.
If you are generating the seed from your own machine, choose either node-id or hardware.
The hardware option tells gadmin to collect information from your machine's hardware as the host signature to generate the license seed. A signature produced by using this parameter will not be altered by software changes on the machine, including OS reinstalls. This is the usual choice.
node-id refers to the machine ID in the machine-id file located at /etc/machine-id and is a unique signature for the OS that identifies your machine. A reinstall of the OS may change the machine ID.
Applying a new license key
Example flow for applying a new license (which may be replacing an existing license key):
1
$ gadmin license set <new_license_key>
2
[   Info] Configuration has been changed. 
3
Please use 'gadmin config apply' to persist the changes.
4
​
5
$ gadmin config apply
6
[Warning] No difference from staging config, config apply is skipped.
7
[   Info] Successfully applied configuration change. Please restart services to make it effective immediately.
8
​
9
$ gadmin restart
10
[   Note] Restart the service(s)? (y/N)y
11
[   Info] Stopping DICT ADMIN GSE NGINX GPE RESTPP KAFKASTRM-LL KAFKACONN TS3SERV GSQL TS3 GUI
12
[   Info] Starting ZK ETCD DICT KAFKA ADMIN GSE NGINX GPE RESTPP KAFKASTRM-LL KAFKACONN TS3SERV GSQL TS3 GUI
Copied!
Once the license has been set and config has been applied, you can run gadmin license status to view the details of your license, including the expiration date and time.
1
$ gadmin license status
2
[Warning] License will expire in 6 days
3
​
4
   Issuer: TigerGraph Inc.
5
 Audience: tigergraph user
6
IssueTime: 2020-06-12 17:45:10 +0000 UTC
7
  EndTime: 2020-06-30 17:45:10 +0000 UTC
8
  Edition: Enterprise
9
​
10
Host:
11
	MaxCPUCore: 1024
12
	MaxPhysicalMemorySize: 1073741824.00MB
13
	MaxClusterNodeNumber: 1024
14
​
15
Topology:
16
	MaxVertexNumber: 9.007199254740991e+15
17
	MaxEdgeNumber: 9.007199254740991e+15
18
	MaxGraphNumber: 1000
19
	MaxTopologySize: 8.00MB
20
​
21
RuntimeMemory:
22
	MaxUserResidentSetSize: 1073741824.00MB
Copied!
gadmin log
The gadmin log command will reveal the location of all commonly checked log files for the TigerGraph system.
1
$ gadmin log -h
2
​
3
List log files of the given services or all services
4
​
5
Usage:
6
  gadmin log [service name...] [flags]
7
​
8
Description:
9
  Service name should be a valid TigerGraph service name, for example, GSE, RESTPP
10
  or GPE.
11
​
12
Flags:
13
  -h, --help   help for log
14
​
15
Global Flags:
16
      --debug   enable debug log output to stdout
Copied!
1
$ gadmin log
2
ADMIN  : /home/tigergraph/tigergraph/log/admin/ADMIN#1.out
3
ADMIN  : /home/tigergraph/tigergraph/log/admin/ADMIN.INFO
4
CTRL   : /home/tigergraph/tigergraph/log/controller/CTRL#1.log
5
CTRL   : /home/tigergraph/tigergraph/log/controller/CTRL#1.out
6
DICT   : /home/tigergraph/tigergraph/log/dict/DICT#1.out
7
DICT   : /home/tigergraph/tigergraph/log/dict/DICT.INFO
8
ETCD   : /home/tigergraph/tigergraph/log/etcd/ETCD#1.out
9
EXE    : /home/tigergraph/tigergraph/log/executor/EXE_1.log
10
EXE    : /home/tigergraph/tigergraph/log/executor/EXE_1.out
11
GPE    : /home/tigergraph/tigergraph/log/gpe/GPE_1#1.out
12
GSE    : /home/tigergraph/tigergraph/log/gse/GSE_1#1.out
13
GSE    : /home/tigergraph/tigergraph/log/gse/log.INFO
14
GSQL   : /home/tigergraph/tigergraph/log/gsql/GSQL#1.out
15
GSQL   : /home/tigergraph/tigergraph/log/gsql/log.INFO
16
GUI    : /home/tigergraph/tigergraph/log/gui/GUI#1.out
17
IFM    : /home/tigergraph/tigergraph/log/informant/IFM#1.log
18
IFM    : /home/tigergraph/tigergraph/log/informant/IFM#1.out
19
KAFKA  : /home/tigergraph/tigergraph/log/kafka/controller.log
20
KAFKA  : /home/tigergraph/tigergraph/log/kafka/kafka-request.log
21
KAFKA  : /home/tigergraph/tigergraph/log/kafka/kafka.log
22
KAFKA  : /home/tigergraph/tigergraph/log/kafka/server.log
23
KAFKA  : /home/tigergraph/tigergraph/log/kafka/state-change.log
24
KAFKACONN: /home/tigergraph/tigergraph/log/kafkaconn/KAFKACONN#1.out
25
KAFKACONN: /home/tigergraph/tigergraph/log/kafkaconn/kafkaconn.log
26
KAFKASTRM-LL: /home/tigergraph/tigergraph/log/kafkastrm-ll/KAFKASTRM-LL_1.out
27
KAFKASTRM-LL: /home/tigergraph/tigergraph/log/kafkastrm-ll/kafkastrm-ll.log
28
NGINX  : /home/tigergraph/tigergraph/log/nginx/logs/NGINX#1.out
29
NGINX  : /home/tigergraph/tigergraph/log/nginx/logs/error.log
30
NGINX  : /home/tigergraph/tigergraph/log/nginx/logs/nginx.access.log
31
NGINX  : /home/tigergraph/tigergraph/log/nginx/logs/nginx.error.log
32
RESTPP : /home/tigergraph/tigergraph/log/restpp/RESTPP#1.out
33
RESTPP : /home/tigergraph/tigergraph/log/restpp/log.INFO
34
TS3    : /home/tigergraph/tigergraph/log/ts3/TS3_1.log
35
TS3    : /home/tigergraph/tigergraph/log/ts3/TS3_1.out
36
TS3SERV: /home/tigergraph/tigergraph/log/ts3serv/TS3SERV#1.out
37
ZK     : /home/tigergraph/tigergraph/log/zk/ZK#1.out
38
ZK     : /home/tigergraph/tigergraph/log/zk/zookeeper.log
Copied!
gadmin reset
1
$ gadmin reset -h
2
​
3
Reset the whole init or given service with its data
4
​
5
Usage:
6
  gadmin reset [service name...] [flags]
7
​
8
Description:
9
  Service name should be a valid TigerGraph service name, for example, GSE, RESTPP
10
  or GPE.
11
​
12
Flags:
13
  -y, --confirm   confirm to reset service
14
  -h, --help      help for reset
15
​
16
Global Flags:
17
      --debug   enable debug log output to stdout
Copied!
gadmin restart
The gadmin restart command is used to restart one, many, or all TigerGraph services. You will need to confirm the restarting of services by either entering y (yes) or n (no). To bypass this prompt, you can use the -y flag to force confirmation.
1
$ gadmin restart -h
2
​
3
Restart services by service id
4
​
5
Usage:
6
  gadmin restart [serviceID...] [flags]
7
​
8
Description:
9
  ServiceID should be [serviceName][_partition][#replica], e.g., GSE_1#3. Leave
10
  replica field empty(e.g. GSE_1) to either refer to all replicas of given
11
  partition, or if the service has no replicas(e.g. EXE_1). Same for parititons.
12
​
13
Flags:
14
  -y, --confirm   confirm to restart service
15
  -h, --help      help for restart
16
      --no-dep    restart service without dependency
17
​
18
Global Flags:
19
      --debug   enable debug log output to stdout
Copied!
1
$ gadmin restart all -y
2
[   Info] Stopping ZK ETCD DICT KAFKA ADMIN GSE NGINX GPE RESTPP KAFKASTRM-LL KAFKACONN TS3SERV GSQL TS3 IFM GUI
3
[   Info] Stopping CTRL
4
[   Info] Stopping EXE
5
[   Info] Starting EXE
6
[   Info] Starting CTRL
7
[   Info] Starting ZK ETCD DICT KAFKA ADMIN GSE NGINX GPE RESTPP KAFKASTRM-LL KAFKACONN TS3SERV GSQL TS3 IFM GUI
Copied!
gadmin start
The gadmin start command can be used to start one, many, or all services.
1
Usage:
2
  gadmin start [serviceID...] [flags]
3
​
4
Description:
5
  ServiceID should be [serviceName][_partition][#replica], e.g., GSE_1#3. Leave
6
  replica field empty(e.g. GSE_1) to either refer to all replicas of given
7
  partition, or if the service has no replicas(e.g. EXE_1). Same for parititons.
8
  If no serviceID is specified, it only starts services excluding the
9
  infrastructure. Use 'gadmin start all' to start all services.
10
​
11
Flags:
12
      --auto-restart         auto restart the service on crash
13
      --dry-run              dry run and output command to start the service
14
  -h, --help                 help for start
15
      --ignore-error         ignore errors when starting services
16
      --no-dep               start service without dependency
17
      --timeout int          request timeout(in MilliSecond) to start the service
18
      --with-config string   start with given config file and dump it to each node (only for executor)
19
​
20
Global Flags:
21
      --debug   enable debug log output to stdout
Copied!
1
$ gadmin start all
2
[   Info] Starting EXE
3
[   Info] Starting CTRL
4
[   Info] Starting ZK ETCD DICT KAFKA ADMIN GSE NGINX GPE RESTPP KAFKASTRM-LL KAFKACONN TS3SERV GSQL TS3 IFM GUI
Copied!
gadmin status
Check the status of TigerGraph component servers:
1
$ gadmin status -h
2
​
3
Show current status of service
4
​
5
Usage:
6
  gadmin status [serviceID...] [flags]
7
​
8
Description:
9
  ServiceID should be [serviceName][_partition][#replica], e.g., GSE_1#3. Leave
10
  replica field empty(e.g. GSE_1) to either refer to all replicas of given
11
  partition, or if the service has no replicas(e.g. EXE_1). Same for parititons.
12
  If no serviceID is specified, it will show all service status
13
​
14
Flags:
15
  -h, --help      help for status
16
  -v, --verbose   report service status in detail
17
​
18
Global Flags:
19
      --debug   enable debug log output to stdout
Copied!
Use gadmin status to report whether each of the main component servers is running (up) or stopped (off). The example below shows the normal status when the graph store is empty and a graph schema has not been defined:
1
$ gadmin status
2
​
3
+--------------------+-------------------------+-------------------------+
4
|    Service Name    |     Service Status      |      Process State      |
5
+--------------------+-------------------------+-------------------------+
6
|       ADMIN        |         Online          |         Running         |
7
|        CTRL        |         Online          |         Running         |
8
|        DICT        |         Online          |         Running         |
9
|        ETCD        |         Online          |         Running         |
10
|        GPE         |         Online          |         Running         |
11
|        GSE         |         Online          |         Running         |
12
|        GSQL        |         Online          |         Running         |
13
|        GUI         |         Online          |         Running         |
14
|        IFM         |         Online          |         Running         |
15
|       KAFKA        |         Online          |         Running         |
16
|     KAFKACONN      |         Online          |         Running         |
17
|    KAFKASTRM-LL    |         Online          |         Running         |
18
|       NGINX        |         Online          |         Running         |
19
|       RESTPP       |         Online          |         Running         |
20
|        TS3         |         Online          |         Running         |
21
|      TS3SERV       |         Online          |         Running         |
22
|         ZK         |         Online          |         Running         |
23
+--------------------+-------------------------+-------------------------+
Copied!
You can also check the status of each instance using the verbose flag : gadmin status -v or gadmin status --verbose. This will show each machine's status. See example below
1
$ gadmin status -v GPE
2
​
3
+--------------------+-------------------------+-------------------------+
4
|    Service Name    |     Service Status      |      Process State      |
5
+--------------------+-------------------------+-------------------------+
6
|      GPE_1#1       |         Warmup          |         Running         |
7
|      GPE_1#2       |         Warmup          |         Running         |
8
+--------------------+-------------------------+-------------------------+
Copied!
Here are the most common service and process status states you might see from running the gadmin status command :
Service Status Definitions
**Online **- The service is online and ready.
**Warmup **- The service is processing the graph information and will be online soon.
**Stopping **- The service has received a stop command and will be down soon.
**Offline **- The service is not available.
**Down **- The service has been stopped or crashed.
**StatusUnknown **- The valid status of the service is not tracked.
Process State Status Definitions
**Init **- Process is initializing and will be in the running state soon.
**Running **- The process is running and available.
**Zombie **- There is a leftover process from a previous instance.
**Stopped **- The process has been stopped or crashed.
**StatusUnknown **- The valid status of the process is not tracked.
gadmin stop
The gadmin stop command can be used to stop one, many, or all TigerGraph services. You will need to confirm the restarting of services by either entering y (yes) or n (no). To bypass this prompt, you can use the -y flag to force confirmation.
1
$ gadmin stop -h
2
​
3
Stop services by service id
4
​
5
Usage:
6
  gadmin stop [serviceID...] [flags]
7
​
8
Description:
9
  ServiceID should be [serviceName][_partition][#replica], e.g., GSE_1#3. Leave
10
  replica field empty(e.g. GSE_1) to either refer to all replicas of given
11
  partition, or if the service has no replicas(e.g. EXE_1). Same for parititons.
12
  If no serviceID is specified, it only stops services excluding the
13
  infrastructure. Use 'gadmin stop all' to stop all services.
14
​
15
Flags:
16
  -y, --confirm   confirm to stop service
17
  -h, --help      help for stop
18
  --ignore-error  stopping services with ignore-error will stop all possible services, and ensure that the platform can still stop and run normally when some services or some nodes are down
19
​
20
Global Flags:
21
      --debug   enable debug log output to stdout
Copied!
1
$ gadmin stop gsql
2
[   Note] Stop the service(s)? (y/N)y
3
[   Info] Stopping GSQL
Copied!
gadmin version
1
$ gadmin version -h
2
​
3
Show the version information
4
​
5
Usage:
6
  gadmin version [flags]
7
​
8
Description:
9
  Show version information of all TigerGraph components, including repo name,
10
  version, git commit number, git commit datetime.
11
​
12
Flags:
13
  -h, --help   help for version
14
​
15
Global Flags:
16
      --debug   enable debug log output to stdout
Copied!
More examples
**Configuring memory use thresholds **
TigerGraph offers two levels of memory thresholds using the following configuration settings:
SysAlertFreePct and SysMinFreePct
SysAlertFreePct setting indicates that the memory usage has crossed a threshold where the system will start throttling Queries to allow long-running queries to finish and release the memory.
SysMinFreePct setting indicates that the memory usage has crossed a critical threshold and the Queries will start aborting automatically to prevent GPE crash and system stability.
By default, SysMinFreePct is set at 10%, at which point Queries will be aborted.​
1
$ gadmin config entry GPE.BasicConfig.Env
2
​
3
GPE.BasicConfig.Env [ LD_PRELOAD=$LD_PRELOAD; LD_LIBRARY_PATH=$LD_LIBRARY_PATH; ]: The runtime environment variables, separated by ';'
4
✔ New: LD_PRELOAD=$LD_PRELOAD; LD_LIBRARY_PATH=$LD_LIBRARY_PATH;
5
​
6
Add this line to the existing config :
7
SysMinFreePct=20;SysAlertFreePct=70;
8
​
9
Your config line should now look like this :
10
​
11
GPE.BasicConfig.Env [ LD_PRELOAD=$LD_PRELOAD; LD_LIBRARY_PATH=$LD_LIBRARY_PATH; ]: The runtime environment variables, separated by ';'
12
✔ New: LD_PRELOAD=$LD_PRELOAD; LD_LIBRARY_PATH=$LD_LIBRARY_PATH;SysMinFreePct=20;SysAlertFreePct=30;
13
​
14
$ gadmin restart gpe -y
Copied!
**Example: **
SysAlertFreePct=30 means when the system memory consumption is over** 70% **of the memory, the system will enter an alert state, and Graph updates will start to slow down.
SysMinFreePct=20 means 20% of the memory is required to be free. When memory consumption enters a critical state (over 80% memory consumption) queries will be aborted. automatically.
Configuring Nginx configuration template​
Follow the steps documented in this support article to update the Nginx configurations of your TigerGraph instance.