# Info Command Reference The info protocol provides access to configuration and statistics for Aerospike Database. You can access the protocol with [clients](https://aerospike.com/download/), over telnet on the info port, or with [`asinfo`](https://aerospike.com/docs/database/tools/asinfo). The examples here use `asinfo`. Starting in Database 7.2: - The error response is standardized on ERROR:ERROR CODE:ERROR STRING. This does not apply to the UDF module. - In the command itself, you can send the parameter as either `ns=` (as before) or `namespace=`.  The older parameter (ns) is deprecated. - Using `ns` or `id` instead of `namespace` is deprecated in Database 7.2. ## Commands #### `alumni-clear-alt` Command: ```bash alumni-clear-alt ``` Descriptions: All neighbor alternate addresses for non-TLS requests (`peers-clear-alt`) this server has ever known of since last restart or since reset via `services-alumni-reset`. Some diagnostic tools, such as `asadm`, have options to use `alumni` to enable full cluster discovery even during cluster disruptions. The `alumni-*` family of commands supersedes the `services-alumni` command. Introduced: 8.1.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, \[ List of endpoints/IPaddresses \]\] Examples: Raw command output ```bash asinfo -v "alumni-clear-alt" 10,3000,[[BB9050011AC4202,,[172.17.0.5]]] ``` Related: [alumni-tls-alt](#alumni-tls-alt)[peers-clear-alt](#peers-clear-alt)[peers-tls-alt](#peers-tls-alt)[services-alumni-reset](#services-alumni-reset) --- #### `alumni-clear-std` Command: ```bash alumni-clear-std ``` Descriptions: Supersedes “services-alumni” for non-TLS service. All neighbor addresses (`peers-clear-std`) this server has ever known about. Some diagnostic tools, eg. asadm, use alumni to enable full cluster view even during cluster disruptions. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, TLSName(ifdefined), \[ List of endpoints/IPaddresses \]\] Examples: Raw command output ```bash asinfo -v "alumni-clear-std" 10,3000,[[BB9050011AC4202,,[172.17.0.5]]] ``` Related: [alumni-tls-std](#alumni-tls-std)[peers-clear-std](#peers-clear-std)[peers-tls-std](#peers-tls-std)[services-alumni-reset](#services-alumni-reset) --- #### `alumni-tls-alt` Command: ```bash alumni-tls-alt ``` Descriptions: All neighbor alternate addresses for TLS requests (`peers-tls-alt`) this server has ever known of since last restart or since reset via `services-alumni-reset`. Some diagnostic tools, such as `asadm`, have options to use `alumni` to enable full cluster discovery even during cluster disruptions. The `alumni-*` family of commands supersedes the `services-alumni` command. Introduced: 8.1.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, TLSName(ifdefined), \[ List of endpoints/IPaddresses \]\] Examples: Raw command output ```bash asinfo -v "alumni-tls-alt" 10,4333,[[BB9050011AC4202,clusternode,[172.17.0.5]]] ``` Related: [alumni-clear-alt](#alumni-clear-alt)[peers-clear-alt](#peers-clear-alt)[peers-tls-alt](#peers-tls-alt)[services-alumni-reset](#services-alumni-reset) --- #### `alumni-tls-std` Command: ```bash alumni-tls-std ``` Descriptions: Supersedes “services-alumni” for TLS service. All neighbor addresses (`peers-tls-std`) this server has ever known about. Some diagnostic tools, eg. asadm, use alumni to enable full cluster view even during cluster disruptions. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, TLSName(ifdefined), \[ List of endpoints/IPaddresses \]\] Examples: Raw command output ```bash asinfo -v "alumni-tls-std" 10,4333,[[BB9050011AC4202,clusternode,[172.17.0.5]]] ``` Related: [alumni-clear-std](#alumni-clear-std)[peers-clear-std](#peers-clear-std)[peers-tls-std](#peers-tls-std)[services-alumni-reset](#services-alumni-reset) --- #### `best-practices` Command: ```bash best-practices ``` Descriptions: Report violated [best-practice](https://aerospike.com/docs/database/install/linux) checks. Introduced: 5.7.0 Deprecated: \- Removed: \- Permission: \- Output: Returns a list of best-practice violations that occurred when the node started. Examples: Raw command output ```bash asinfo -v "best-practices" failed_best_practices=min-free-kbytes,swappiness ``` --- #### `bins` Command: ```bash bins/[NAMESPACE] ``` Descriptions: bin usage information and used bin names for all or a particular namespace. Introduced: 3.3.0 Deprecated: \- Removed: 7.0.0 Permission: \- Parameters: NAMESPACE Where NAMESPACE is the name of a namespace that exists on this server. Output: Without NAMESPACE stats and names for each namespace. Namespace names are suffixed with a colon ’:’ and the bin stats and names are comma ’,’ separated. Bin stat names and values are separated by an equals ’=’. The end of stats list is delimited by a semicolon ’;’ and may be followed by more namespaces. --- With NAMESPACE Returns comma ’,’ separated statistics and bin names for the provided namespace. Statistics are separated from their values by an equals ’=’. Examples: Without NAMESPACE ```bash asinfo -v 'bins' test:num-bin-names=7,bin-names-quota=65535,str_100_bin, str_uniq_bin,int_uniq_bin,seed,dynamic_str,dynamic_int, fill_bin; asinfo -v 'bins' test:num-bin-names=7,bin-names-quota=32768,str_100_bin, str_uniq_bin,int_uniq_bin,seed,dynamic_str,dynamic_int, fill_bin; ``` --- With NAMESPACE ```bash asinfo -v 'bins/test' num-bin-names=7,bin-names-quota=65535,str_100_bin, str_uniq_bin,int_uniq_bin,seed,dynamic_str, dynamic_int,fill_bin asinfo -v 'bins/test' num-bin-names=7,bin-names-quota=32768,str_100_bin, str_uniq_bin,int_uniq_bin,seed,dynamic_str, dynamic_int,fill_bin ``` Related: [namespace](#namespace)[namespaces](#namespaces)[sets](#sets)[statistics](#statistics) --- #### `build` Command: ```bash build ``` Descriptions: Returns the build ID, or release, for the server. In `asadm`, the table generated by [`info network`](https://aerospike.com/docs/database/tools/asadm/live-mode/#network) contains this information under _Build_. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Output: Aerospike build ID (release) of the server Release format: epoch.major.minor.patch Examples: Execute Command ```bash asinfo -v 'build' 8.1.1.0 ``` --- #### `build_arch` Command: ```bash build_arch ``` Descriptions: Returns the CPU architecture the server was built for. Deprecated in Database 8.1.1.0. Use [`release`](https://aerospike.com/docs/database/reference/info#release) instead. Introduced: 3.3.0 Deprecated: 8.1.1.0 Removed: \- Permission: \- Output: CPU architecture, such as _x86\_64_ or _aarch64_ Examples: Execute Command ```bash asinfo -v 'build_arch' x86_64 ``` Related: [release](#release) --- #### `build_ee_sha` Command: ```bash build_ee_sha ``` Descriptions: Returns the Git commit SHA of the enterprise server build. Only available in Aerospike Enterprise Edition. Deprecated in Database 8.1.1.0. Use [`release`](https://aerospike.com/docs/database/reference/info#release) instead. Introduced: 3.3.0 Deprecated: 8.1.1.0 Removed: \- Permission: \- Output: Git commit SHA (40 character hex string) Examples: Execute Command ```bash asinfo -v 'build_ee_sha' ab9381954cadda812c026f5bc7c48630e94cd4ed ``` Related: [release](#release) --- #### `build_os` Command: ```bash build_os ``` Descriptions: Returns the operating system the server was built for. Deprecated in Database 8.1.1.0. Use [`release`](https://aerospike.com/docs/database/reference/info#release) instead. Introduced: 3.3.0 Deprecated: 8.1.1.0 Removed: \- Permission: \- Output: Operating system name, such as _debian13_, _el8_, _ubuntu22.04_ Examples: Execute Command ```bash asinfo -v 'build_os' debian13 ``` Related: [release](#release) --- #### `build_sha` Command: ```bash build_sha ``` Descriptions: Returns the Git commit SHA of the community/core server build. Deprecated in Database 8.1.1.0. Use [`release`](https://aerospike.com/docs/database/reference/info#release) instead. Introduced: 3.3.0 Deprecated: 8.1.1.0 Removed: \- Permission: \- Output: Git commit SHA (40 character hex string) Examples: Execute Command ```bash asinfo -v 'build_sha' 88aebec58aafa8a1245e61d650a955699d2d2b0b ``` Related: [release](#release) --- #### `build_time` Command: ```bash build_time ``` Descriptions: Returns the timestamp when the server was built. Deprecated in Database 8.1.1.0. Introduced: 3.3.0 Deprecated: 8.1.1.0 Removed: \- Permission: \- Output: Build timestamp string Examples: Execute Command ```bash asinfo -v 'build_time' Wed Jul 2 05:41:49 PM PDT 2025 ``` Related: [release](#release) --- #### `cluster-stable` Command: ```bash cluster-stable:size=TARGET_CLUSTER_size;ignore-migrations=TRUE/FALSE;namespace=NAMESPACE_NAME ``` Descriptions: The command checks if a node’s cluster-state has stabilized. A user typically runs this command across all nodes in the cluster to check if all nodes have converged to the same cluster state by checking that none of the nodes return an error and that they all return the same [`cluster_key`](https://aerospike.com/docs/database/reference/metrics#node_stats__cluster_key). In asadm, the table generated by [`info network`](https://aerospike.com/docs/database/tools/asadm/live-mode/#network) contains this information under “Cluster”. Introduced: 4.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: size Target size of the cluster to check the cluster-state for. --- ignore-migrations If migration state needs to be ignored when checking for cluster stability. Valid values are `true` or `false`. Default is `false` which does not ignore migrations. --- namespace Name of the namespace to check the cluster-state for. Not specifying the namespace will check across all namespaces. Output: Returns the current ‘cluster\_key’ when the following are satisfied: - If ‘size’ is specified then the target node’s ‘cluster-size’ must match size. - If ‘ignore-migrations’ is either unspecified or ‘false’ then the target node’s migrations counts must be zero for the provided ‘namespace’ or all namespaces if ‘namespace’ is not provided. Examples: Execute Command ```bash Admin+> asinfo -v "cluster-stable:ignore-migrations=true;size=3;namespace=test" 10.0.100.xxx:3000 returned: 7A54B93FDB52 10.0.100.yyy:3000 returned: 7A54B93FDB52 10.0.100.zzz:3000 returned: 7A54B93FDB52 ``` --- #### `dc/DC_NAME` Command: ```bash dc/DC_NAME ``` Descriptions: Returns the XDR statistics specific to each XDR destination. Introduced: 3.6.0 Deprecated: \- Removed: 5.0.0 Permission: \- Output: Returns the statistics such as the state of the destination, the timelag, the number of shipping and delete attempts to each remote datacenter etc. These are valid and available for the datacenters defined in the XDR stanza on the source cluster. Examples: Database 3.8.0 to 5.0.0 ```bash asinfo -v dc/REMOTE_DC_1 -l dc_state=CLUSTER_UP dc_timelag=0 dc_rec_ship_attempts=58374 dc_delete_ship_attempts=0 dc_remote_ship_ok=58121 dc_err_ship_client=38 dc_err_ship_server=0 dc_esmt_bytes_shipped=5662278 dc_esmt_ship_avg_comp_pct=0.00 dc_latency_avg_ship=0 dc_remote_ship_avg_sleep=0.000 dc_open_conn=192 dc_recs_inflight=216 dc_size=3 ``` --- Up to Database 3.7.5 ```bash asinfo -v dc/REMOTE_DC_1 -p 3004 -l xdr-dc-state=CLUSTER_UP xdr-dc-timelag=0 xdr-dc-rec-ship-attempts=0 xdr-dc-delete-ship-attempts=0 esmt-bytes-shipped-compression=0 esmt-ship-compression=0.00% lst-main=1459856431988 lst-windowship=18446744073709551615 lst-failednode=18446744073709551615 lst-localmin=0 ``` --- #### `dcs` Command: ```bash dcs ``` Descriptions: Returns the list of datacenters configured in the XDR context. This includes the inactive DC’s and empty skeletons too. Introduced: \- Deprecated: \- Removed: 5.0.0 Permission: \- Examples: List of configured datacenters in XDR context ```bash asinfo -v 'dcs' DC2;DC3;DC4;DC5;DC6;DC7 ``` --- #### `dump-skew` Command: ```bash dump-skew: ``` Descriptions: Print out clock skew information across the cluster nodes. Introduced: 4.0.0 Deprecated: \- Removed: \- Permission: sys-admin Output: The clock skew for the cluster. Examples: Print clock skew between nodes in the log ```bash asinfo -v 'dump-skew:' ok May 03 2018 23:54:09 GMT: INFO (skew): (skew_monitor.c:587) CSM: cluster-clock-skew:0 May 03 2018 23:54:09 GMT: INFO (skew): (skew_monitor.c:598) CSM: node:bb997a7833e1600 hlc-delta:0 May 03 2018 23:54:09 GMT: INFO (skew): (skew_monitor.c:598) CSM: node:bb96544c23e1600 hlc-delta:0 May 03 2018 23:54:09 GMT: INFO (skew): (skew_monitor.c:598) CSM: node:bb93fe99a3e1600 hlc-delta:0 ``` --- #### `edition` Command: ```bash edition ``` Descriptions: Returns the Aerospike edition installed on the server. Deprecated in Database 8.1.1.0. Use [`release`](https://aerospike.com/docs/database/reference/info#release) instead. Introduced: 3.3.0 Deprecated: 8.1.1.0 Removed: \- Permission: \- Output: Aerospike edition, such as _Aerospike Enterprise Edition_ or _Aerospike Community Edition_ Examples: Execute Command ```bash asinfo -v 'edition' Aerospike Enterprise Edition ``` Related: [release](#release) --- #### `eviction-reset` Command: ```bash eviction-reset:namespace=NAMESPACE_NAME ``` Descriptions: Available in Database 4.5.1 and later. Removes a namespace’s eviction void time entry in the associated SMD (System Meta Data) file. This allows some previously evicted records to be resurrected on a subsequent cold restart (only those records that have not had their persisted storage block overwritten by other records). This means that the prior eviction depth for the namespace is no longer enforced — subsequent NSUP cycles evict again with a recomputed eviction depth when another breach occurs. Introduced: 4.5.1 Deprecated: \- Removed: \- Permission: data-admin Parameters: namespace Name of the namespace for which to reset eviction. Output: ok Examples: Reset eviction for namespace test ```bash asinfo -v 'eviction-reset:namespace=test' ``` --- #### `feature-key` Command: ```bash feature-key ``` Descriptions: For the Database Enterprise Edition, returns the contents of the [`feature-key-file`](https://aerospike.com/docs/database/reference/config#service__feature-key-file) (excluding the signature) at the time the server started. For the Community Edition, returns the string `null`. Introduced: 4.0.0 Deprecated: \- Removed: \- Permission: \- Output: Items are separated by semicolons (default) or with the `-l` option, newlines. Examples: List feature keys ```bash asinfo -v 'feature-key' -l feature-key-version=2 serial-number=XXXXXXXX valid-until-date=2021-12-31 valid-until-version=5.6 acc-command-center-app=true acc-command-center-api=true asdb-change-notification=true asdb-cluster-nodes-limit=20 asdb-compression=true asdb-encryption-at-rest=true asdb-ldap=true asdb-pmem=true asdb-strong-consistency=true mesg-jms-connector=true mesg-kafka-connector=true raf-realtime-analysis-framework=true ``` --- #### `get-config` Command: ```bash get-config[:context=CONTEXT] get-config:context=namespace<;namespace=NAMESPACE_NAME> ``` Descriptions: Returns running configuration for all or a particular context. The equivalent command in asadm is [`show config`](https://aerospike.com/docs/database/tools/asadm/live-mode/#config-1). Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: context Configuration context to retrieve. Options: - namespace - network - security - service - xdr If context is not included the behavior returns configuration for all contexts excluding namespaces. --- namespace Used for namespace context only. Name of the namespace to get the configuration for. Output: Security Report Sinks In Database 5.6.0 and later, the `log` and `syslog` subcontext configuration parameters are reported individually, similar to other configuration parameters. However, in Database 5.5.0 and earlier, these parameters are reported in an aggregated format, as represented below. “Security Report Sinks” show the settings of the `log` and `syslog` subcontexts of the `security` context. The corresponding configuration parameters do not have the `-sinks` suffix: - [`report-authentication`](https://aerospike.com/docs/database/reference/config#security__report-authentication)`-sinks` - [`report-data-op`](https://aerospike.com/docs/database/reference/config#security__report-data-op)`-sinks` - [`report-sys-admin`](https://aerospike.com/docs/database/reference/config#security__report-sys-admin)`-sinks` - [`report-user-admin`](https://aerospike.com/docs/database/reference/config#security__report-user-admin)`-sinks` - [`report-violation`](https://aerospike.com/docs/database/reference/config#security__report-violation)`-sinks` The values summarize the parameters’ true/false settings. The possible values are (default is 0): - 0: `false` in both the `log` and `syslog` subcontexts. - 1: `true` only in the `log` subcontext. - 2: `true` only in `syslog` subcontext. - 3: `true` in both subcontexts. Examples: Retrieve configuration for all contexts ```bash asinfo -v "get-config" -l advertise-ipv6=false auto-pin=none batch-index-threads=4 batch-max-buffers-per-queue=255 batch-max-requests=5000 batch-max-unused-buffers=256 cluster-name=null debug-allocationamespace=none disable-udf-execution=false downgrading=false enable-benchmarks-fabric=false enable-health-check=false enable-hist-info=false enforce-best-practices=false feature-key-file[0]=/etc/aerospike/features.conf indent-allocationamespace=false info-threads=16 keep-caps-ssd-health=false log-local-time=false log-millis=false microsecond-histograms=false: migrate-fill-delay=0 migrate-max-num-incoming=4 migrate-threads=1 min-cluster-size=1 node-id=BB90DAD00290C00 node-id-interface=null os-group-perms=false pidfile=null proto-fd-idle-ms=0 proto-fd-max=15000 query-max-done=100 query-threads-limit=128 run-as-daemon=true salt-allocationamespace=false service-threads=20 sindex-builder-threads=4 sindex-gc-period=10 stay-quiesced=false ticker-interval=10 transaction-max-ms=1000 transaction-retry-ms=1002 vault-ca=null vault-path=null vault-token-file=null vault-url=null work-directory=/opt/aerospike service.access-port=0 service.address=any service.alternate-access-port=0 service.port=3000 service.tls-port=0 service.tls-access-port=0 service.tls-alternate-access-port=0 service.tls-name=null service.disable-localhost=false heartbeat.mode=multicast heartbeat.multicast-group=239.1.99.222 heartbeat.port=9918 heartbeat.multicast-ttl=0 heartbeat.interval=150 heartbeat.timeout=10 heartbeat.connect-timeout-ms=500 heartbeat.mtu=1500 heartbeat.protocol=v3 fabric.tls-port=0 fabric.tls-name=null fabric.channel-bulk-fds=2 fabric.channel-bulk-recv-threads=4 fabric.channel-ctrl-fds=1 fabric.channel-ctrl-recv-threads=4 fabric.channel-meta-fds=1 fabric.channel-meta-recv-threads=4 fabric.channel-rw-fds=8 fabric.channel-rw-recv-pools=1 fabric.channel-rw-recv-threads=16 fabric.keepalive-enabled=true fabric.keepalive-intvl=1 fabric.keepalive-probes=10 fabric.keepalive-time=1 fabric.port=3001 fabric.recv-rearm-threshold=1024 fabric.send-threads=8 info.port=3003 ``` --- Retrieve network configuration. ```bash asinfo -v 'get-config:context=network' -l ``` --- Retrieve configuration for namespace test. ```bash asinfo -v 'get-config:context=namespace;namespace=test' -l ``` --- For Database 5.0.0, display the XDR configuration of all defined datacenters. ```bash asinfo -h hostIPaddress -v "get-config:context=xdr" ``` --- Same command with asadm. ```bash Admin+> asinfo -h hostIPaddress -v "get-config:context=xdr" ``` --- For Database 5.0.0+, display the XDR configuration of a specific datacenter and all its namespaces. (Starting with Database 7.2.0, use “namespace=NAME” instead of id=NAME”.\`) ```bash asinfo -h hostIPaddress -v "get-config:context=xdr;dc=DC1" ``` --- For Database 5.0.0+, display the XDR configuration a specific datacenter and a specific namespace. (Starting with Database 7.2.0, use \`get-config\` “namespace=NAME”.\`) ```bash asinfo -h hostIPaddress -v "get-config:context=xdr;dc=DC1;namespace=test" ``` Related: [namespace](#namespace)[set-config](#set-config) --- #### `get-dc-config` Command: ```bash get-dc-config ``` Descriptions: Returns the configurations for the XDR datacenters. For each datacenter, this lists the following information: - Database 3.8.0 to 4.9: Name of the DC, seeded destination nodes, internal to external IP mappings (if any), alternate services list in use or not, and namespaces configured to ship to the DC. Introduced: 3.6.0 Deprecated: \- Removed: 5.0.0 Permission: \- Output: Return value is in the following format: Database 4.7.0.2 to 4.9: ```asciidoc dc-name=DC_NAME:dc-typeAEROSPIKE|HTTP:tls-name=TLS_NAME:dc-security-config-file= nodes=IP+PORT:auth-mode=:int-ext-ipmap=INTERNAL-IP|EXTERNAL-IP: dc-connectionamespace=CONNECTIONS:dc-connections-idle-ms=IDLE_TIME:dc-use-alternate-services=TRUE|FALSE: namespaces=NS1,NS2,NS3; ``` Database 4.5.0.1 to 4.7.0.2: ```asciidoc dc-name=DC_NAME:dc-typeAEROSPIKE|HTTP:tls-name=TLS_NAME:dc-security-config-file= nodes=IP+PORT:int-ext-ipmap=INTERNAL-IP|EXTERNAL-IP: dc-connectionamespace=CONNECTIONS:dc-connections-idle-ms=IDLE_TIME:dc-use-alternate-services=TRUE|FALSE: namespaces=NS1,NS2,NS3; ``` Database 4.4.0.4 and 4.5.0.1: ```asciidoc dc-name=DC_NAME:dc-typeAEROSPIKE|HTTP:tls-name=TLS_NAME:nodes=IP+PORT:int-ext-ipmap=INTERNAL-IP|EXTERNAL-IP: dc-connectionamespace=CONNECTIONS:dc-connections-idle-ms=IDLE_TIME:dc-use-alternate-services=TRUE|FALSE: namespaces=NS1,NS2,NS3; ``` Database 3.15.0.1 TO 4.4.0.4: ```asciidoc dc-name=DC_NAME:nodes=IP+PORT:int-ext-ipmap=INTERNAL-IP|EXTERNAL-IP: dc-connectionamespace=CONNECTIONS:dc-connections-idle-ms=IDLE_TIME:dc-use-alternate-services=TRUE|FALSE: tls-name=TLS_NAME:namespaces=NS1,NS2,NS3; ``` Examples: Database 4.7.0.2 to 4.9 ```bash asinfo -v get-dc-config dc-name=REMOTE_DC:dc-type=aerospike:tls-name=:dc-security-config-file=/private/aerospike/security_credentials_REMOTE_DC.txt:\ nodes=192.168.100.140+3000,192.168.100.147+3000:auth-mode=internal:int-ext-ipmap=:dc-connectionamespace=64:\ dc-connections-idle-ms=55000:dc-use-alternate-services=false:namespaces=test ``` --- Database 4.5.0.1 to 4.7.0.2 ```bash asinfo -v get-dc-config dc-name=REMOTE_DC:dc-type=aerospike:tls-name=:dc-security-config-file=/private/aerospike/security_credentials_REMOTE_DC.txt:\ nodes=192.168.100.140+3000,192.168.100.147+3000:int-ext-ipmap=:dc-connections=64:\ dc-connections-idle-ms=55000:dc-use-alternate-services=false:namespaces=test ``` --- Database 4.4.0.4 to 4.5.0.1 ```bash asinfo -v get-dc-config dc-name=REMOTE_DC:dc-type=aerospike:tls-name=:\ nodes=192.168.100.140+3000,192.168.100.147+3000:int-ext-ipmap=:dc-connections=64:\ dc-connections-idle-ms=55000:dc-use-alternate-services=false:namespaces=test ``` --- Database3.15.0.1 to 4.4.0.4 ```bash asinfo -v get-dc-config dc-name=REMOTE_DC:nodes=192.168.100.140+3000,192.168.100.147+3000:int-ext-ipmap=:dc-connectionamespace=64:\ dc-connections-idle-ms=55000:dc-use-alternate-services=false:tls-name=:namespaces=test ``` --- #### `get-stats` Command: ```bash get-stats:context=xdr;dc=dataCenterName ``` Descriptions: Returns the statistics for remote datacenters defined in the `xdr` of the specified host. Introduced: 5.0.0 Deprecated: \- Removed: \- Permission: \- Output: Returns a semi-colon-delimited-value list of datacenter statistics, such as the state of the destination, the timelag, the number of shipping and delete attempts to each remote datacenter defined in the XDR stanza on the source cluster. Examples: Show consolidated stats for all namespaces for datacenter someDataCenterName. (Starting with Database 7.2.0, use “namespace=NAME” instead of ns=NAME”.\`) ```bash asinfo -v "get-stats:context=xdr;dc=someDataCenterName" -l ``` --- Show XDR stats per datacenter, per namespace for datacenter DATA\_CENTER\_NAME. (Starting with Database 7.2.0, use “namespace=NAME” instead of ns=NAME”.\`) ```bash asinfo -v "get-stats:context=xdr;dc=DATA_CENTER_NAME;namespace=NAMESPACE_NAME" -l ``` --- #### `health-outliers` Command: ```bash health-outliers ``` Descriptions: Returns list of outliers and their information. Requires that [`enable-health-check`](https://aerospike.com/docs/database/reference/config#service__enable-health-check) be enabled first. Compares metrics for each host to the same metrics on other nodes within the cluster. For instance, it compares how the replication latency for a given host compares to the cluster-wide distribution of replication latencies. Using a statistical approach, we can estimate with confidence how anomalous a point is. In simple terms, the farther a node’s metric is from existing points, the more likely it signals an issue. - The distributions are calculated using [Interquartile ranges](https://en.wikipedia.org/wiki/Interquartile_range). - A minimum of four nodes are required. At least three data points are necessary to flag one of them as an outlier. - Metrics used are replication latency, device read latency, fabric connections opened, node arrivals, and proxies. - For a statistic to be part of the outlier detection algorithm, the value must be greater than a minimum threshold. The minimum thresholds for different statistics are listed on the [Health monitor page](https://aerospike.com/docs/database/observe/health-check/). Introduced: 4.3.1.3 Deprecated: \- Removed: \- Permission: \- Output: Returns a list of tuples. - `id`\= Either node ID or the device ID which is declared as an outlier. - `confidence-pct`\= Metric when high denotes that the stat is highly skewed. - `reason`\= Description of the stat that is responsible for declaring id as an outlier. Examples: Execute Command ```bash asinfo -v 'health-outliers' -l id=bb9040011ac4202:confidence_pct=100:reason=fabric_connections_opened id=bb9040011ac4202:confidence_pct=100:reason=proxies id=bb9040011ac4202:confidence_pct=100:reason=node_arrivals id=/opt/aerospike/data/bar2.dat:namespace=test:confidence_pct=100:reason=device_read_latency ``` --- #### `health-stats` Command: ```bash health-stats ``` Descriptions: Returns list of stats maintained by health-stats for reference. Requires that [`enable-health-check`](https://aerospike.com/docs/database/reference/config#service__enable-health-check) be enabled first. Introduced: 4.3.1.3 Deprecated: \- Removed: \- Permission: \- Output: Returns list of tuples.b - stat=… Identifies the type of statistics. - value=… Current moving average. - node=… Node id. - device=… Device name, and the value for device\_read\_latency is in microseconds. - namespace= Optional entry. Specifies the namespace corresponding to the statistic. Examples: Execute Command ```bash asinfo -v 'health-stats' -l stat=fabric_connections_opened:value=0:node=BB9070011AC4202 stat=fabric_connections_opened:value=0:node=BB9030011AC4202 stat=fabric_connections_opened:value=0:node=BB9050011AC4202 stat=fabric_connections_opened:value=153:node=BB9040011AC4202 stat=test_device_read_latency:value=1408:device=/opt/aerospike/data/bar1.dat:namespace=test stat=test_device_read_latency:value=306132:device=/opt/aerospike/data/bar2.dat:namespace=test stat=test_device_read_latency:value=11630:device=/opt/aerospike/data/bar3.dat:namespace=test ``` --- #### `hist-track-start` Command: ```bash hist-track-start:[back=BACK;slice=SLICE;thresholds=THRESHOLDS;hist=HIST] ``` Descriptions: Start or Restart histogram tracking. Introduced: 3.9.0 Deprecated: \- Removed: 5.1.0 Permission: sys-admin Parameters: hist Histogram name - if none is provided, command applies to all namespace tracked histograms, which are the read, write, UDF and query histograms’. \[Default: all namespace tracked histograms\] Options (`ns` being the namespace name): - {ns}-read - {ns}-write - {ns}-udf - {ns}-query - batch-index See [Monitoring latencies](https://aerospike.com/docs/database/observe/latency) for more information about histograms. --- back Total time span in seconds over which to cache data. \[Default: aerospike.conf value if defined, otherwise mandatory\] --- slice Period in seconds at which to cache histogram data. \[Default: aerospike.conf value if defined, otherwise 10\] --- thresholds Comma-separated bucket (ms) values to track, must be powers of 2. eg. 1,4,16,64 \[Default: aerospike.conf value if defined, otherwise 1,8,64\] Output: On success returns “ok”, use `get-config` to confirm settings. To persist settings update `aerospike.conf`. Examples: Configure reads histogram ```bash asinfo -v 'hist-track-start:hist={ns}-read;back=43200;slice=30;thresholds=1,4,16,64;' ok ``` --- Configure all histograms ```bash asinfo -v 'hist-track-start:hist={ns}-read;back=43200;thresholds=1,2,4,8,16,32;' ok ``` Related: [hist-track-stop](#hist-track-stop)[latency](#latency)[throughput](#throughput) --- #### `hist-track-stop` Command: ```bash hist-track-stop:[hist=HIST] ``` Descriptions: Stop histogram tracking. Introduced: 3.9.0 Deprecated: \- Removed: 5.1.0 Permission: sys-admin Parameters: hist Histogram name - if none is provided, command applies to all namespace tracked histograms, which are the read, write, UDF and query histograms’. \[Default: all namespace tracked histograms\] Options (`ns` being the namespace name): - {ns}-read - {ns}-write - {ns}-udf - {ns}-query - batch-index To know more about histograms, see [Monitoring latencies](https://aerospike.com/docs/database/observe/latency). Output: On success returns “ok”, use `get-config` to confirm settings. To persist settings update aerospike.conf. Examples: Stop UDF histogram collection ```bash asinfo -v 'hist-track-stop:hist={ns}-udf' ok ``` --- Stop all histogram collection ```bash asinfo -v 'hist-track-stop:' ok ``` Related: [hist-track-start](#hist-track-start)[latency](#latency)[throughput](#throughput) --- #### `histogram` Command: ```bash histogram:namespace=NAMESPACE_NAME;[set=SET;]type=TYPE ``` Descriptions: Returns a histogram snapshot for a namespace\[/set\] and histogram type. Prior to Database 4.5.1, the ttl histogram is computed by the namespace supervisor (NSUP), and is updated every NSUP interval or duration of an NSUP cycle (whichever is longer), while the object-size and object-size-linear histograms are updated every `object-size-hist-period` (default is 1 hour). Starting with Database 4.5.1, all of these histograms are computed by NSUP and updated every [nsup-hist-period](https://aerospike.com/docs/database/reference/config#namespace__nsup-hist-period) (default is 1 hour). Prior to Database 5.3.0, the object-size and object-size-linear histograms are not available for namespaces with [storage-engine](https://aerospike.com/docs/database/reference/config#namespace__storage-engine) `memory`. Introduced: 4.2.0.2 Deprecated: \- Removed: \- Permission: \- Parameters: namespace Name of the _namespace_ to retrieve a histogram from. --- type Type of histogram to be retrieved. Options: - ttl - Time to live distribution of records represented as a linear histogram. - object-size - Size distribution of objects (non-tombstones records) represented as a logarithmic histogram. - object-size-linear - Size distribution of objects (non-tombstones records) represented as a linear histogram. Object size histogram counts include replicas and are based on the compressed size of the objects if compression is used. To find the number of unique objects falling into a particular histogram band, divide by the replication factor. TTL histogram puts the non expirable records in the first bucket. To find the number of expirable records in the first bucket, subtract the [non\_expirable\_objects](https://aerospike.com/docs/database/reference/metrics#namespace__non_expirable_objects) from it. --- set (Optional) Name of a particular _set_ to retrieve a histogram from. Output: Linear Histograms Types: ttl, object-size-linear Returns a linear histogram with the following format: `units=UNITS:hist-width=HIST-WIDTH:bucket-width=BUCKET-WIDTH:buckets=BUCKETS;` Where: - UNITS: The unit type being represented. Notice that for object-size, the unit is ‘bytes’ not ‘rblocks’. - HIST-WIDTH: The total size of the entire histogram. - BUCKET-WIDTH: The size of an individual bucket. - BUCKETS: 1024 comma separated counters for object-size-linear, 100 for TTL. --- Logarithmic Histograms Types: object-size Returns a logarithmic histogram with the following format: `units=UNITS:INTERVALS` Where: - **UNITS**: The unit type being represented. Notice that for object-size, the unit is bytes’ not ‘rblocks’. - **INTERVALS**: Only intervals having a value greater than 0 are shown. Interval keys use interval notation where ’\[’ means that it begins and includes this value and ’)’ means it ends at, but does not include that value. The value for each key is the number of elements that fall within this interval. Notice that the intervals will also include an SI unit such as K=\[2^10 to 2^20), M=\[2^20 to 2^30), G=\[2^30 to 2^40), T=\[2^40 to 2^50), P=\[2^50 to 2^60\], E=\[2^60 to 2^70). Values exceeding 8E (8 Exaunits) are placed in the last bucket which would be represented as \[8E-inf). Examples: Logarithmic 'Object Size' histogram for namespace 'test' ```bash asinfo -v 'histogram:type=object-size;namespace=test' units=bytes:[64-128)=2964:[64K-128K)=1234 ``` --- Linear 'Object Size' histogram for namespace 'test' ```bash asinfo -v 'histogram:type=object-size-linear;namespace=test' units=bytes:hist-width=8388608:bucket-width=8192:buckets=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,505,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 ``` --- Linear 'Time to Live' histogram for namespace 'test' ```bash asinfo -v 'histogram:namespace=test;type=ttl' units=seconds:hist-width=2588700:bucket-width=25887:buckets=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,517 ``` --- Linear 'Time to Live' histogram for set 'testset' of namespace 'test' ```bash asinfo -v 'histogram:namespace=test;set=testset;type=ttl' units=seconds:hist-width=2588700:bucket-width=25887:buckets=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,500 ``` --- #### `index-pressure` Command: ```bash index-pressure ``` Descriptions: Display index dirty pages. The two numbers shown in the output give the total amount of memory and the amount of memory in dirty pages (not flushed to disk). The command is most useful when the primary index is on disk. The command gives an idea of how far behind the write back process, where pages in RAM are written back to disk, is running. If the write back process runs too far behind, dirty pages accumulate in RAM and eventually the system runs out of memory. This command provides a means of tracking that. Introduced: 4.8.0 Deprecated: \- Removed: \- Permission: \- Examples: Display index pressure ```bash $ asinfo -l -v index-pressure test:1630212096:69632 ``` --- #### `jem-stats` Command: ```bash jem-stats:file=path_to_file;sites=path_to_file ``` Descriptions: Dump information about `jemalloc`, the subsystem used by Aerospike to manage memory allocations, into flat files. Introduced: 3.0.0 Deprecated: \- Removed: \- Permission: sys-admin Output: Dumps information about memory allocation to `file` and locations in which `asd` is allocating memory to `sites`. This information may be requested by Aerospike Support to help troubleshoot unexpected memory usage. Examples: Dump detailed allocation information to \`/tmp/jem.txt\` and \`/tmp/sites.txt\`. ```bash asinfo -v 'jem-stats:file=/tmp/jem.txt;sites=/tmp/sites.txt' ``` --- #### `jobs` Command: ```bash jobs: jobs:module=MODULE jobs:module=MODULE;cmd=COMMAND;trid=TRANSACTIONID jobs:module=MODULE;cmd=COMMAND;trid=TRANSACTIONID;value=VALUE ``` Descriptions: Command and Control for queries and scans.The equivalent command in asadm is [`show jobs`](https://aerospike.com/docs/database/tools/asadm/live-mode#jobs). Note: this command is deprecated as of Database 5.7.0. For scan and query management with Database 5.7.0 or later, the recommended commands are [scan-show](https://aerospike.com/docs/database/reference/info#scan-show), [scan-abort](https://aerospike.com/docs/database/reference/info#scan-abort), [query-show](https://aerospike.com/docs/database/reference/info#query-show), and [query-abort](https://aerospike.com/docs/database/reference/info#query-abort). Introduced: 4.9.0 Deprecated: 5.7.0 Removed: 6.3.0 Permission: data-admin Parameters: cmd Action to execute against a particular transaction. Requires data-admin or sys-admin privileges for security enabled clusters. Options: - get-job - kill-job - set-priority --- module Name of the module to query statistics or execute a command on. Options: - scan - query - sindex-builder - Removed in Database 5.7.0 --- trid Unique Identification number for a scan or query transaction. Use either “jobs:” or “jobs:module=MODULE” forms to find Transaction IDs. --- value Value to provide to the command. Output: Module Scan --- Command Executions Commands do not acknowledge success, but will acknowledge failure. --- Job Status Responses - active(ok) – In Progress - done(ok) – Completed with no error - done(user-aborted) – Scan aborted by user - done(abandoned-unknown) – Scan aborted with unknown failure - done(abandoned-cluster-key) – Scan aborted due to cluster key change - done(abandoned-response-error) – Scan aborted due to response error - done(abandoned-response-timeout) – Scan aborted due to timeout Examples: Query All Job Stats ```bash asinfo -v "jobs:" -l module=scan:trid=1225169085971291877:job-type=basic:namespace=test:priority=1:n-pids-requested=1:status=done(abandoned-\ response-error):job-progress=12.38:run-time=1003:time-since-done=120794:recs-read=73362:net-i\ o-bytes=11864041:socket-timeout=30000:from=98.76.543.21+2005 module=scan:trid=6741947622470254455:job-type=basic:namespace=test:set=MySetName1:priority=1:n-pids-requested=1:status=\ done(ok):job-progress=100.00:run-time=192:time-since-done=154105:recs-read=17251:net-io-bytes\ =2253844:socket-timeout=30000:from=98.76.543.21+2005 module=scan:trid=6106310598564268407:job-type=basic:namespace=test:set=MySetName1:priority=1:n-pids-requested=1:status=\ done(ok):job-progress=100.00:run-time=149:time-since-done=302042:recs-read=3431:net-io-bytes=\ 456324:socket-timeout=10000:from=98.76.543.21+2005 module=sindex-builder:trid=3:job-type=sindex-build:namespace=test:set=MySetName1:priority=2:status=d\ one(ok):job-progress=100.00:run-time=185:time-since-done=463265:recs-read=6555:net-io-bytes=0\ :socket-timeout=0:sindex-name=IdxName3 module=sindex-builder:trid=2:job-type=sindex-build:namespace=test:set=MySetName1:priority=2:status=d\ one(ok):job-progress=100.00:run-time=153:time-since-done=502038:recs-read=6555:net-io-bytes=0\ :socket-timeout=0:sindex-name=IdxName2 module=sindex-builder:trid=1:job-type=sindex-build:namespace=test:set=MySetName1:priority=2:status=d\ one(ok):job-progress=100.00:run-time=213:time-since-done=530942:recs-read=6555:net-io-bytes=0\ :socket-timeout=0:sindex-name=IdxName1 ``` --- Request All Scan Stats ```bash asinfo -v 'jobs:module=scan' -l module=scan:trid=15685911422701175574:job-type=basic:\ namespace=test:set=scan1_e1:priority=0:n-pids-requested=1:\ rps=0:active-threads=0:status=done(ok):job-progress=100.00:\ run-time=0:time-since-done=12611917:recs-throttled=0:\ recs-filtered-meta=0:recs-filtered-binamespace=0:recs-succeeded=0:\ recs-failed=0:net-io-bytes=68:socket-timeout=10000:\ from=192.168.200.227+35660 ``` Related: [statistics](#statistics) --- #### `latencies` Command: ```bash latencies:[hist=histogramName;] ``` Descriptions: Returns latency data for all enabled histograms, or a single histogram if one is specified. Only the most recent time slice (as governed by the ticker interval) is tracked. These histograms contain 17 latency buckets (ranging from 0 to 216 time units) and all are displayed, following the scale tag (for example, `msec`) and the transactions-per-second value. The equivalent command in asadm is [`show latencies`](https://aerospike.com/docs/database/tools/asadm/live-mode#latencies). All enabled benchmarks can be tracked in Database 5.1.0 and later. Prior to Database 5.1.0 track only the auto-enabled benchmarks through the info protocol. For information about benchmark histograms, see [Histograms from Aerospike Logs](https://aerospike.com/docs/database/observe/latency). If latency data is unavailable (if no transaction of that type has taken place), only the histogram name is printed. Example: ```plaintext asinfo -v 'latencies:hist={test}-read' {test}-read: ``` Introduced: 5.1.0 Deprecated: \- Removed: \- Permission: \- Parameters: hist Histogram name - if none is provided, command applies to the auto-enabled benchmarks. \[Default: all auto-enabled benchmarks\] Options: - {NAMESPACE}-batch-sub-read - {NAMESPACE}-batch-sub-write - {NAMESPACE}-batch-sub-udf - {NAMESPACE}-re-repl - {NAMESPACE}-read - {NAMESPACE}-udf - {NAMESPACE}-write - {NAMESPACE}-pi-query - {NAMESPACE}-si-query Output: Return value is in the following format: `histogramName_0:timeUnit,ops/sec,threshOld_0,threshOld_1,...;histogramName_1:...` Examples: Show all default histograms ```bash asinfo -v 'latencies:' -l batch-index: {test}-read:msec,1.5,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-write:msec,5.6,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-udf:msec,1.7,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-batch-sub-read:msec,1.2,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-batch-sub-write: {test}-batch-sub-udf:msec,1.4,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-pi-query: {test}-si-query: ``` --- Show read latency histogram ```bash asinfo -v 'latencies:hist={test}-read' {test}-read:msec,10.0,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 ``` --- Show write histograms with write benchmarks enabled ```bash asinfo -v 'latencies:hist={test}-benchmarks-write' -l {test}-write-start:msec,341.9,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-write-restart:msec,0.0,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-write-dup-res:msec,0.0,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-write-master:msec,341.9,58.53,1.35,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-write-repl-write:msec,0.0,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 {test}-write-response:msec,342.0,0.03,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00 ``` --- #### `latency` Command: ```bash latency:[hist=HISTOGRAM;][back=BACK;][duration=DURATION;][slice=SLICE] ``` Descriptions: The `latency` command was replaced by [`latencies`](https://aerospike.com/docs/database/reference/info#latencies) in Database 5.1.0 and removed in Database 5.2.0.
1ms,>8ms,>64ms 23:53:48,5234.4,0.54,0.02,0.00 {ns}-write:23:53:38-GMT,ops/sec,>1ms,>8ms,>64ms 23:53:48,354.7,2.34,0.77,0.00 error-no-data-yet-or-back-too-small error-no-data-yet-or-back-too-small ``` --- Show Read Latency Histogram ```bash asinfo -v 'latency:hist={ns}-read;slice=30;back=300;duration:120' {ns}-read:23:50:28-GMT,ops/sec,>1ms,>8ms,>64ms;23:50:58,0.0,0.00,0.00,0.00; 23:51:28,0.0,0.00,0.00,0.00;23:51:58,0.0,0.00,0.00,0.00;23:52:28,0.0,0.00,0.00,0.00; 23:52:58,0.0,0.00,0.00,0.00;23:53:28,0.0,0.00,0.00,0.00;23:53:58,0.0,0.00,0.00,0.00; 23:54:28,0.0,0.00,0.00,0.00;23:54:58,0.0,0.00,0.00,0.00 ``` Related: [hist-track-start](#hist-track-start)[hist-track-stop](#hist-track-stop)[throughput](#throughput) --- #### `log-set` Command: ```bash log-set:id=SINK_ID;CONTEXT=VERBOSITY ``` Descriptions: Sets verbosity for logging contexts. `set-log` is a synonym. The equivalent command in asadm is [`manage config logging`](https://aerospike.com/docs/database/tools/asadm/live-mode/#manage). Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: sys-admin Parameters: SINK\_ID The log identifier to make a verbosity change on. See `logs` for a list of SINK\_IDs. --- CONTEXT The logging context to make a verbosity change on. See `log` for a list of CONTEXTs. --- VERBOSITY The verbosity level to make the selected context. Options: - critical - warning - info - debug - detail Output: Returns ‘ok’ on success. To config change see `log`. Examples: Set verbosity of fabric context to debug ```bash asinfo -v 'log-set:id=0;fabric=debug' ok ``` Related: [log](#log)[logs](#logs) --- #### `log` Command: ```bash log/ log//CONTEXT ``` Descriptions: Returns a list of logging contexts and their associated verbosity levels. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: LOG Identifier for the logged component. --- CONTEXT (Optional) Which logging context to query the verbosity. Output: If a CONTEXT is not provided Returns Semicolon ’;’ delimited list of CONTEXT:VERBOSITY --- If a CONTEXT is provided Returns requested CONTEXT:VERBOSITY Examples: Query Verbosity Level of Fabric ```bash asinfo -v 'log/0/fabric' fabric:INFO ``` Related: [logs](#logs)[log-set](#log-set) --- #### `logs` Command: ```bash logs ``` Descriptions: Returns a list of log file locations in use by this server. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Output: List of log “Sink IDs” and their associated output location Examples: Execute Command ```bash asinfo -v 'logs' 0:/var/log/aerospike/aerospike.log ``` Related: [log](#log)[log-set](#log-set) --- #### `masking-show` Command: ```bash masking-show[:namespace=NAMESPACE[;set=SET_NAME]] ``` Descriptions: Returns all masking rules. Does not require elevated permissions. Introduced: 8.1.1 Deprecated: \- Removed: \- Permission: \- Parameters: namespace Filter masking rules by namespace. \[Optional\] --- set Filter masking rules by set. \[Optional\] Output: Semicolon-delimited list of masking rules in the cluster. Examples: Show all masking rules ```bash asinfo -v masking-show namespace=test;set=users;bin=ssn;type=string;function=redact;position=0;length=6 ``` --- Show masking rules filtered by namespace ```bash asinfo -v "masking-show:namespace=test" namespace=test;set=users;bin=ssn;type=string;function=redact;position=0;length=6 ``` Related: [masking](#masking) --- #### `masking` Command: ```bash masking ``` Descriptions: Adds, deletes, or changes the masking function to be applied for a given path. Requires `masking-admin` permissions. Introduced: 8.1.1 Deprecated: \- Removed: \- Permission: \- Parameters: namespace The namespace where the masking rule applies. \[Required\] --- set The set where the masking rule applies. \[Required\] --- bin The bin where the masking rule applies. \[Required\] --- type The data type of the bin. \[Optional\] Defaults to `string`. Options: - `string` - `integer` - `bool` - `float` --- function The masking function to apply. \[Required\] Options: - `remove` - Remove this masking rule. - `redact` - Mask as a redacted string. Supports `position`, `length`, and `value` parameters. - `constant` - Mask as a constant value. Supports the `value` parameter. --- position Used with `function=redact`. The position in the string to start the redaction. A positive integer (0 or greater) is counted from the start of the string. A negative integer is counted from the end, with -1 being the last character in the string. \[Optional\] Defaults to 0. --- length Used with `function=redact`. How many characters of the string to redact starting at `position`. \[Optional\] By default, redacts to the end of the string. --- value Used with `function=redact` or `function=constant`. For `redact`: The character to use for redaction. Defaults to `*`. For `constant`: The value to use for the mask. By default, the string is masked as an empty string. \[Optional\] Acceptable values are the printable ASCII characters 33-126 excluding `=`,`;`, and `:`. If violated, some Aerospike features and tools may not function properly. Examples: Set or remove redact masking method ```bash masking:namespace=test;set=users;bin=ssn;type=string;function=redact masking:namespace=test;set=users;bin=ssn;type=string;function=remove ``` Related: [masking-show](#masking-show) --- #### `mcast` Command: ```bash mcast ``` Descriptions: Returns the heartbeat address and port when the server heartbeat mode is multicast. Deprecated since Database 8.1.0. Use the network context of `get-config` instead. Introduced: 3.3.0 Deprecated: 8.1.0 Removed: \- Permission: \- Output: MULTICAST\_IP:MULTICAST\_PORT for the target Aerospike server. Examples: Execute Command ```bash asinfo -v 'mcast' 239.1.98.29:9918 ``` Related: [mesh](#mesh) --- #### `mesh` Command: ```bash mesh ``` Descriptions: Returns the heartbeat address and port when the server heartbeat mode is `mesh`. Deprecated since Database 8.1.0. Use the network context of `get-config` instead. Introduced: 3.3.0 Deprecated: 8.1.0 Removed: \- Permission: \- Output: HOST\_IP:MESH\_PORT for the target Aerospike server. Examples: Execute Command ```bash asinfo -v 'mesh' 172.16.121.138:3002 ``` Related: [mcast](#mcast)[tip](#tip)[tip-clear](#tip-clear) --- #### `namespace` Command: ```bash namespace/NAMESPACE ``` Descriptions: Returns health and usage stats for a particular namespace. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: NAMESPACE The namespace name to query for associated [`configuration parameters`](https://aerospike.com/docs/database/reference/config) and [`statistics`](https://aerospike.com/docs/database/reference/metrics). Some direct links for a couple of such entries: [`replication-factor`](https://aerospike.com/docs/database/reference/config#namespace__replication-factor), [`memory-size`](https://aerospike.com/docs/database/reference/config#namespace__memory-size), [`objects`](https://aerospike.com/docs/database/reference/metrics#namespace__objects)[`evicted_objects`](https://aerospike.com/docs/database/reference/metrics#namespace__evicted_objects). Examples: Database 6.0.0 and later ```bash asinfo -v 'namespace/test'-ll s_cluster_size=1 effective_replication_factor=1 objects=500 tombstones=0 xdr_tombstones=0 xdr_bin_cemeteries=0 master_objects=500 master_tombstones=0 prole_objects=0 prole_tombstones=0 non_replica_objects=0 non_replica_tombstones=0 unreplicated_records=0 dead_partitionamespace=0 unavailable_partitionamespace=0 clock_skew_stop_writes=false stop_writes=false hwm_breached=false truncating=false current_time=382320584 non_expirable_objects=0 expired_objects=0 evicted_objects=0 evict_ttl=0 evict_void_time=0 smd_evict_void_time=0 nsup_cycle_duration=0 truncate_lut=382320545369 truncated_records=2216 sindex_gc_cleaned=0 memory_used_bytes=2342144 memory_used_data_bytes=0 memory_used_index_bytes=32000 memory_used_set_index_bytes=0 memory_used_sindex_bytes=2310144 memory_free_pct=99 xmem_namespace=1 available_bin_names=65471 device_total_bytes=2147483648 device_used_bytes=64800 device_free_pct=99 device_available_pct=98 cache_read_pct=0 storage-engine.file[0].used_bytes=64800 storage-engine.file[0].free_wblocks=253 storage-engine.file[0].write_q=0 storage-engine.file[0].writes=1 storage-engine.file[0].defrag_q=0 storage-engine.file[0].defrag_reads=0 storage-engine.file[0].defrag_writes=0 storage-engine.file[0].shadow_write_q=0 storage-engine.file[0].age=-1 record_proto_uncompressed_pct=0.000 record_proto_compression_ratio=1.000 query_proto_uncompressed_pct=0.000 query_proto_compression_ratio=1.000 pending_quiesce=false effective_is_quiesced=false nodes_quiesced=0 effective_prefer_uniform_balance=true migrate_tx_partitions_imbalance=0 migrate_tx_instances=0 migrate_rx_instances=0 migrate_tx_partitions_active=0 migrate_rx_partitions_active=0 migrate_tx_partitions_initial=0 migrate_tx_partitions_remaining=0 migrate_tx_partitions_lead_remaining=0 migrate_rx_partitions_initial=0 migrate_rx_partitions_remaining=0 migrate_records_skipped=0 migrate_records_transmitted=0 migrate_record_retransmits=0 migrate_record_receives=0 migrate_signals_active=0 migrate_signals_remaining=0 appeals_tx_active=0 appeals_rx_active=0 appeals_tx_remaining=0 appeals_records_exonerated=0 client_tsvc_error=0 client_tsvc_timeout=0 client_proxy_complete=0 client_proxy_error=0 client_proxy_timeout=0 client_read_success=2476 client_read_error=1 client_read_timeout=0 client_read_not_found=5 client_read_filtered_out=79 client_write_success=8412 client_write_error=18 client_write_timeout=0 client_write_filtered_out=1 xdr_client_write_success=0 xdr_client_write_error=0 xdr_client_write_timeout=0 client_delete_success=2684 client_delete_error=1 client_delete_timeout=0 client_delete_not_found=103 client_delete_filtered_out=1 xdr_client_delete_success=0 xdr_client_delete_error=0 xdr_client_delete_timeout=0 xdr_client_delete_not_found=0 client_udf_complete=36 client_udf_error=3 client_udf_timeout=0 client_udf_filtered_out=1 client_lang_read_success=27 client_lang_write_success=9 client_lang_delete_success=0 client_lang_error=3 from_proxy_tsvc_error=0 from_proxy_tsvc_timeout=0 from_proxy_read_success=0 from_proxy_read_error=0 from_proxy_read_timeout=0 from_proxy_read_not_found=0 from_proxy_read_filtered_out=0 from_proxy_write_success=0 from_proxy_write_error=0 from_proxy_write_timeout=0 from_proxy_write_filtered_out=0 xdr_from_proxy_write_success=0 xdr_from_proxy_write_error=0 xdr_from_proxy_write_timeout=0 from_proxy_delete_success=0 from_proxy_delete_error=0 from_proxy_delete_timeout=0 from_proxy_delete_not_found=0 from_proxy_delete_filtered_out=0 xdr_from_proxy_delete_success=0 xdr_from_proxy_delete_error=0 xdr_from_proxy_delete_timeout=0 xdr_from_proxy_delete_not_found=0 from_proxy_udf_complete=0 from_proxy_udf_error=0 from_proxy_udf_timeout=0 from_proxy_udf_filtered_out=0 from_proxy_lang_read_success=0 from_proxy_lang_write_success=0 from_proxy_lang_delete_success=0 from_proxy_lang_error=0 batch_sub_tsvc_error=0 batch_sub_tsvc_timeout=0 batch_sub_proxy_complete=0 batch_sub_proxy_error=0 batch_sub_proxy_timeout=0 batch_sub_read_success=959 batch_sub_read_error=0 batch_sub_read_timeout=0 batch_sub_read_not_found=51 batch_sub_read_filtered_out=1 batch_sub_write_success=0 batch_sub_write_error=0 batch_sub_write_timeout=0 batch_sub_write_filtered_out=0 batch_sub_delete_success=0 batch_sub_delete_error=0 batch_sub_delete_timeout=0 batch_sub_delete_not_found=0 batch_sub_delete_filtered_out=0 batch_sub_udf_complete=0 batch_sub_udf_error=0 batch_sub_udf_timeout=0 batch_sub_udf_filtered_out=0 batch_sub_lang_read_success=0 batch_sub_lang_write_success=0 batch_sub_lang_delete_success=0 batch_sub_lang_error=0 from_proxy_batch_sub_tsvc_error=0 from_proxy_batch_sub_tsvc_timeout=0 from_proxy_batch_sub_read_success=0 from_proxy_batch_sub_read_error=0 from_proxy_batch_sub_read_timeout=0 from_proxy_batch_sub_read_not_found=0 from_proxy_batch_sub_read_filtered_out=0 from_proxy_batch_sub_write_success=0 from_proxy_batch_sub_write_error=0 from_proxy_batch_sub_write_timeout=0 from_proxy_batch_sub_write_filtered_out=0 from_proxy_batch_sub_delete_success=0 from_proxy_batch_sub_delete_error=0 from_proxy_batch_sub_delete_timeout=0 from_proxy_batch_sub_delete_not_found=0 from_proxy_batch_sub_delete_filtered_out=0 from_proxy_batch_sub_udf_complete=0 from_proxy_batch_sub_udf_error=0 from_proxy_batch_sub_udf_timeout=0 from_proxy_batch_sub_udf_filtered_out=0 from_proxy_batch_sub_lang_read_success=0 from_proxy_batch_sub_lang_write_success=0 from_proxy_batch_sub_lang_delete_success=0 from_proxy_batch_sub_lang_error=0 udf_sub_tsvc_error=0 udf_sub_tsvc_timeout=0 udf_sub_udf_complete=497 udf_sub_udf_error=0 udf_sub_udf_timeout=0 udf_sub_udf_filtered_out=160 udf_sub_lang_read_success=52 udf_sub_lang_write_success=304 udf_sub_lang_delete_success=141 udf_sub_lang_error=0 ops_sub_tsvc_error=0 ops_sub_tsvc_timeout=0 ops_sub_write_success=114 ops_sub_write_error=0 ops_sub_write_timeout=0 ops_sub_write_filtered_out=0 dup_res_ask=0 dup_res_respond_read=0 dup_res_respond_no_read=0 retransmit_all_read_dup_res=0 retransmit_all_write_dup_res=0 retransmit_all_write_repl_write=0 retransmit_all_delete_dup_res=0 retransmit_all_delete_repl_write=0 retransmit_all_udf_dup_res=0 retransmit_all_udf_repl_write=0 retransmit_all_batch_sub_dup_res=0 retransmit_udf_sub_dup_res=0 retransmit_udf_sub_repl_write=0 retransmit_ops_sub_dup_res=0 retransmit_ops_sub_repl_write=0 pi_query_short_basic_complete=0 pi_query_short_basic_error=0 pi_query_short_basic_timeout=0 pi_query_long_basic_complete=36 pi_query_long_basic_error=0 pi_query_long_basic_abort=0 pi_query_aggr_complete=0 pi_query_aggr_error=0 pi_query_aggr_abort=0 pi_query_udf_bg_complete=7 pi_query_udf_bg_error=0 pi_query_udf_bg_abort=0 pi_query_ops_bg_complete=2 pi_query_ops_bg_error=0 pi_query_ops_bg_abort=0 si_query_short_basic_complete=0 si_query_short_basic_error=0 si_query_short_basic_timeout=0 si_query_long_basic_complete=24 si_query_long_basic_error=1 si_query_long_basic_abort=0 si_query_aggr_complete=6 si_query_aggr_error=0 si_query_aggr_abort=0 si_query_udf_bg_complete=1 si_query_udf_bg_error=0 si_query_udf_bg_abort=0 si_query_ops_bg_complete=2 si_query_ops_bg_error=0 si_query_ops_bg_abort=0 geo_region_query_reqs=2 geo_region_query_cells=24 geo_region_query_points=0 geo_region_query_falsepos=0 re_repl_success=0 re_repl_error=0 re_repl_timeout=0 fail_xdr_forbidden=0 fail_key_busy=0 fail_generation=3 fail_record_too_big=0 fail_client_lost_conflict=0 fail_xdr_lost_conflict=0 deleted_last_bin=2 allow-ttl-without-nsup=false background-query-max-rps=10000 conflict-resolution-policy=generation conflict-resolve-writes=false data-in-index=false default-ttl=0 disable-cold-start-eviction=false disable-write-dup-res=false disallow-null-setname=false enable-benchmarks-batch-sub=false enable-benchmarks-ops-sub=false enable-benchmarks-read=false enable-benchmarks-udf=false enable-benchmarks-udf-sub=false enable-benchmarks-write=false enable-hist-proxy=false evict-hist-buckets=10000 evict-tenths-pct=5 high-water-disk-pct=0 high-water-memory-pct=0 ignore-migrate-fill-delay=false index-stage-size=1073741824 index-type=shmem max-record-size=0 memory-size=2147483648 migrate-order=5 migrate-retransmit-ms=5000 migrate-sleep=1 nsup-hist-period=3600 nsup-period=120 nsup-threads=1 partition-tree-sprigs=256 prefer-uniform-balance=true rack-id=0 read-consistency-level-override=off reject-non-xdr-writes=false reject-xdr-writes=false replication-factor=1 single-bin=false single-query-threads=4 stop-writes-pct=90 strong-consistency=false strong-consistency-allow-expunge=false tomb-raider-eligible-age=86400 tomb-raider-period=86400 transaction-pending-limit=20 truncate-threads=4 write-commit-level-override=off xdr-bin-tombstone-ttl=86400 xdr-tomb-raider-period=120 xdr-tomb-raider-threads=1 storage-engine=device storage-engine.file[0]=/etc/aerospike/test.dat storage-engine.cache-replica-writes=false storage-engine.cold-start-empty=false storage-engine.commit-to-device=false storage-engine.commit-min-size=0 storage-engine.compression=none storage-engine.compression-level=0 storage-engine.data-in-memory=false storage-engine.defrag-lwm-pct=50 storage-engine.defrag-queue-min=0 storage-engine.defrag-sleep=1000 storage-engine.defrag-startup-minimum=0 storage-engine.direct-files=false storage-engine.disable-odsync=false storage-engine.enable-benchmarks-storage=false storage-engine.encryption-key-file=null storage-engine.encryption-old-key-file=null storage-engine.filesize=2147483648 storage-engine.flush-max-ms=1000 storage-engine.max-write-cache=67108864 storage-engine.min-avail-pct=5 storage-engine.post-write-queue=256 storage-engine.read-page-cache=false storage-engine.scheduler-mode=null storage-engine.serialize-tomb-raider=false storage-engine.sindex-startup-device-scan=false storage-engine.tomb-raider-sleep=1000 storage-engine.write-block-size=8388608 sindex.num-partitionamespace=32 geo2dsphere-within.strict=true geo2dsphere-within.min-level=1 geo2dsphere-within.max-level=20 geo2dsphere-within.max-cells=12 geo2dsphere-within.level-mod=1 geo2dsphere-within.earth-radius-meters=6371000 ``` Related: [bins](#bins)[namespaces](#namespaces)[set-config](#set-config)[sets](#sets) --- #### `namespaces` Command: ```bash namespaces ``` Descriptions: Returns a list namespaces defined on this server. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Output: Semicolon ’;’ delimited list of namespace names defined on this server Examples: Execute Command ```bash asinfo -v 'namespaces' test;bar ``` Related: [bins](#bins)[namespace](#namespace)[sets](#sets) --- #### `node` Command: ```bash node ``` Descriptions: Node ID. Unique 15 character hex string for each node based on the mac address and port. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Output: Returns the Node ID for this server. Examples: Execute Command ```bash asinfo -v 'node' BB9C5014A290C00 ``` --- #### `peers-clear-alt` Command: ```bash peers-clear-alt ``` Descriptions: Supersedes “services-alternate” for non-TLS, alternate addresses. List of alternate service addresses of peer nodes. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, TLSName(if defined), \[ List of endpoints/IPaddresses \]\] Examples: Execute Command ```bash asinfo -v "peers-clear-alt" 9,3000,[[BB9060011AC4202,,[74.125.239.53]],[BB9070011AC4202,,[74.125.239.54]]] ``` Related: [peers-clear-std](#peers-clear-std)[peers-tls-alt](#peers-tls-alt)[peers-tls-std](#peers-tls-std)[service-clear-alt](#service-clear-alt)[service-clear-std](#service-clear-std)[service-tls-alt](#service-tls-alt)[service-tls-std](#service-tls-std) --- #### `peers-clear-std` Command: ```bash peers-clear-std ``` Descriptions: Supersedes “services” for non-TLS, standard addresses. List of addresses of neighbor cluster nodes to advertise for Application to connect. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, TLSName(if defined), \[ List of endpoints/IPaddresses \]\] Examples: Execute Command ```bash asinfo -v "peers-clear-std" 9,3000,[[BB9040011AC4202,,[172.17.0.4]],[BB9050011AC4202,,[172.17.0.5]]] ``` Related: [peers-clear-alt](#peers-clear-alt)[peers-tls-alt](#peers-tls-alt)[peers-tls-std](#peers-tls-std)[service-clear-alt](#service-clear-alt)[service-clear-std](#service-clear-std)[service-tls-alt](#service-tls-alt)[service-tls-std](#service-tls-std) --- #### `peers-generation` Command: ```bash peers-generation ``` Descriptions: Returns the generation count of the services lists (peers-clear-std, peers-tls-std). Each node in the cluster maintains a generation count of its services list. This value is incremented for every change in its services list, such as node addition/removal. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Examples: Execute Command ```bash asinfo -v "peers-generation" 10 ``` Related: [peers-clear-std](#peers-clear-std)[peers-tls-std](#peers-tls-std) --- #### `peers-tls-alt` Command: ```bash peers-tls-alt ``` Descriptions: Supersedes “services-alternate” for TLS, alternate addresses. List of alternate service addresses of peer nodes. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, TLSName(if defined), \[ List of endpoints/IPaddresses \]\] Examples: Execute Command ```bash asinfo -v "peers-tls-alt" 9,4333,[[BB9060011AC4202,clusternode,[74.125.239.53]],[BB9070011AC4202,clusternode,[74.125.239.54]]] ``` Related: [peers-clear-alt](#peers-clear-alt)[peers-clear-std](#peers-clear-std)[peers-tls-std](#peers-tls-std)[service-clear-alt](#service-clear-alt)[service-clear-std](#service-clear-std)[service-tls-alt](#service-tls-alt)[service-tls-std](#service-tls-std) --- #### `peers-tls-std` Command: ```bash peers-tls-std ``` Descriptions: Supersedes “services” for TLS, standard addresses. List of addresses of neighbor cluster nodes to advertise for Application to connect. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Output: Returns peers-generation, port, list of \[ NodeIDs/Names, TLSName(if defined), \[ List of endpoints/IPaddresses \]\] Examples: Execute Command ```bash asinfo -v "peers-tls-std" 9,4333,[[BB9040011AC4202,clusternode,[172.17.0.4]],[BB9050011AC4202,clusternode,[172.17.0.5]]] ``` Related: [peers-clear-alt](#peers-clear-alt)[peers-clear-std](#peers-clear-std)[peers-tls-alt](#peers-tls-alt)[service-clear-alt](#service-clear-alt)[service-clear-std](#service-clear-std)[service-tls-alt](#service-tls-alt)[service-tls-std](#service-tls-std) --- #### `query-abort-all` Command: ```bash query-abort-all: ``` Descriptions: Abort all queries running on the server node. This command kills all queries running across all the namespaces. Introduced: 5.7.0 Deprecated: \- Removed: \- Permission: data-admin Output: Returns “OK - number of queries killed: x” where x is the number of aborted queries. Examples: Abort all queries ```bash asinfo -v 'query-abort-all:' OK - number of queries killed: 7 ``` Related: [query-abort](#query-abort)[query-show](#query-show) --- #### `query-abort` Command: ```bash query-abort:trid=TRANSACTIONID ``` Descriptions: Abort a query running on the server node. Introduced: 5.7.0 Deprecated: \- Removed: \- Permission: data-admin Parameters: trid Transaction ID to identify the query to abort. This parameter is required. Output: Returns “Ok” if the query was aborted, otherwise “Transaction Not Found”. Examples: Abort a query ```bash asinfo -v 'query-abort:trid=1225169085971291877' Ok ``` Related: [query-show](#query-show) --- #### `query-show` Command: ```bash query-show query-show:trid=TRANSACTIONID ``` Descriptions: Returns information about current/recent queries on the server node. The equivalent command in asadm is [`show jobs queries`](https://aerospike.com/docs/database/tools/asadm/live-mode#jobs). Introduced: 5.7.0 Deprecated: \- Removed: \- Permission: \- Parameters: trid Transaction ID to identify a particular query. If this parameter is omitted, information is returned about every running monitored query, as well as all completed monitored queries, up to the limit specified by [query-max-done](https://aerospike.com/docs/database/reference/config#service__query-max-done). Output: Query Information Query information includes: - trid - transaction ID of the query - job-type - type of query, one of: - basic - aggregation - background-udf - background-ops - ns - name of queried namespace - set - name of queried set, (only appears if the query specifies a set) - sindex-name - name of the secondary index for the query (only appears with Database 6.1.0+) - n-pids-requested - number of partitions requested for the query (only appears if non-zero) - rps - query rate (records per second) requested for the query - active-threads - number of threads currently processing the query - status - query status, one of: - active (ok) - in progress - done (ok) - completed successfully - done (user-aborted) - aborted by user - done (abandoned-unknown) - abandoned with unknown failure - done (abandoned-response-error) - aborted due to error responding to a client - done (abandoned-response-timeout) - aborted due to timeout responding to client - job-progress - estimated query completion percentage - run-time - how long the query has taken (or how long it took), in milliseconds - time-since-done - how long ago the query finished, in milliseconds - recs-throttled - number of records examined by the query for throttling purposes - recs-filtered-meta - number of records filtered out by an [expression](https://aerospike.com/docs/develop/expressions) at the metadata level - recs-filtered-bins - number of records filtered out by an [expression](https://aerospike.com/docs/develop/expressions) at the bin level - recs-succeeded - number of records successfully processed by the query - recs-failed - number of query records that failed processing (for example, unreadable) - net-io-bytes - amount of response data sent, in bytes - net-io-time - time taken to send response data, in milliseconds - socket-timeout - socket timeout for the query, in milliseconds - from - origin of the query request (ip-address and port) - udf-filename - name of the UDF source file (background-udf queries only) - udf-function - name of the UDF function (background-udf queries only) - udf-active - number of active UDF transactions (background-udf queries only) - ops-active - number of active background ops transactions (background-ops queries only) Examples: Get information about a query ```bash asinfo -v 'query-show:trid=17933252198779880811' -l trid=17933252198779880811 job-type=basic ns=test set=eg-set sindex-name=test-bin-index n-pids-requested=4096 rps=0 active-threads=0 status=done(ok) job-progress=100.00 run-time=3 time-since-done=1317562 recs-throttled=0 recs-filtered-meta=0 recs-filtered-bins=0 recs-succeeded=1 recs-failed=0 net-io-bytes=150 net-io-time=0 socket-timeout=30000:from=127.0.0.1+37994 ``` Related: [query-abort](#query-abort)[scan-show](#scan-show) --- #### `quiesce-undo` Command: ```bash quiesce-undo ``` Descriptions: Revert the effects of the [`quiesce`](https://aerospike.com/docs/database/reference/info#quiesce) on the next recluster event. The command is ignored if [`stay-quiesced`](https://aerospike.com/docs/database/reference/config#service__stay-quiesced) is true for the node. Introduced: 4.3.1 Deprecated: \- Removed: \- Permission: sys-admin Output: On success returns OK. Examples: Execute Command ```bash Admin+> asinfo -v 'quiesce-undo:' with 192.168.100.233 192.168.100.233:3000 (192.168.100.233) returned: ok ``` Related: [recluster](#recluster)[quiesce](#quiesce) --- #### `quiesce` Command: ```bash quiesce ``` Descriptions: Cause a node to avoid participating as a replica after the next recluster event. Quiescing and reclustering before removing a node from the cluster prevents client timeouts that may otherwise happen when a node drops from the cluster. Quiescing can also help when decommissioning one or more nodes and it is desirable to maintain full replication during the decommissioning process. Refer to the [Quiesce Node](https://aerospike.com/docs/database/manage/cluster/quiesce-node) page for further details. The command fails if [`stay-quiesced`](https://aerospike.com/docs/database/reference/config#service__stay-quiesced) is true for the node. The equivalent command in `asadm` is [`manage quiesce`](https://aerospike.com/docs/database/tools/asadm/live-mode#quiesce). Introduced: 4.3.1 Deprecated: \- Removed: \- Permission: sys-admin Output: On success returns OK. Examples: Execute Command ```bash Admin+> asinfo -v 'quiesce:' with 192.168.100.233 192.168.100.233:3000 (192.168.100.233) returned: ok ``` Related: [recluster](#recluster)[quiesce-undo](#quiesce-undo) --- #### `racks` Command: ```bash racks: ``` Descriptions: Enterprise only feature as of Database 4.0.0. Returns the rack grouping of nodes for each namespace. Introduced: 3.1.03.0 Deprecated: \- Removed: \- Permission: \- Parameters: namespace Name of the namespace to query rack grouping for. Output: For each namespace, list the number of unique racks, each followed by the node\_ids in the rack. Examples: Execute Command ```bash asinfo -v 'racks:' namespace=test:rack_1=BCD10DFA9290C00,BB910DFA9290C00:rack_2=BD710DFA9290C00,BC310DFA9290C00 ``` --- #### `recluster` Command: ```bash recluster: ``` Descriptions: Force the cluster to advance the cluster key and rebalance. Processed by the acting principal node and ignored by other nodes. It is safe and recommended to issue the command to all the nodes in the cluster through asadm. By using this command, certain configurations can now take effect without a node restart. For example, no restart is necessary when used when setting roster in strong consistency mode or applying rack awareness changes. - When issued to a cluster with no pending migrations and no configuration changes, this command should not generate new migrations. - When issued to a cluster with no pending migrations, but has its rack-id dynamically changed, this command generates new migrations. - When issued to a cluster with ongoing migrations: - Cancels active migrations - this can be used to lower migrate threads-related configuration ([`migrate-threads`](https://aerospike.com/docs/database/reference/config#service__migrate-threads) / [`migrate-max-num-incoming`](https://aerospike.com/docs/database/reference/config#service__migrate-max-num-incoming)) with immediate effect. The downside is you must re-process any partitions that were partially completed. - New initial migrations should not exceed the last observed pending migrations. There are known cases where the command is expected to fail. Contact Aerospike Support for details. The rack awareness feature is only in the Aerospike Enterprise Edition as of Database 4.0.0. Introduced: 3.14.1.1 Deprecated: \- Removed: \- Permission: sys-admin Output: On success returns OK. Examples: Execute Command ```bash Admin+> asinfo -v 'recluster:' 192.168.100.233:3000 (192.168.100.233) returned: ok 192.168.100.215:3000 (192.168.100.215) returned: ignored-by-non-principal ``` --- #### `release` Command: ```bash release ``` Descriptions: Returns release information for this server in a single command, consolidating the following legacy commands: [`edition`](https://aerospike.com/docs/database/reference/info#edition), [`version`](https://aerospike.com/docs/database/reference/info#version), [`build_os`](https://aerospike.com/docs/database/reference/info#build_os), [`build_arch`](https://aerospike.com/docs/database/reference/info#build_arch), [`build_sha`](https://aerospike.com/docs/database/reference/info#build_sha), [`build_ee_sha`](https://aerospike.com/docs/database/reference/info#build_ee_sha) Introduced: 8.1.1.0 Deprecated: \- Removed: \- Permission: \- Output: Semicolon-separated key-value pairs containing release information: - `edition` - The Aerospike edition, such as _Aerospike Enterprise Edition_ - `version` - The Database version number, such as _8.1.1.0_. - `os` - The operating system the build was compiled for, such as _debian13_ - `arch` - The CPU architecture, such as _x86\_64_ - `sha` - The Git commit SHA of the community/core build - `ee-sha` - The Git commit SHA of the enterprise build (Enterprise Edition only) - `fips-sha` - The Git commit SHA of the Federal Edition build (Federal Edition only) Examples: Execute Command ```bash asinfo -v 'release' edition=Aerospike Enterprise Edition;version=8.1.1.0;os=debian13;arch=x86_64;sha=88aebec58aafa8a1245e61d650a955699d2d2b0b;ee-sha=ab9381954cadda812c026f5bc7c48630e94cd4ed;fips-sha=107d0788a85a5919d165d7ec56d2e4171bc7c078 ``` Related: [build](#build) --- #### `replicas-all` Command: ```bash replicas-all ``` Descriptions: Displays a bitmap of the all partitions. Use `asadm’s` `show pmap` instead, which gives the human-readable equivalent. Deprecated since Database 8.1.0 in favor of the `replicas` info command. Deprecated: 8.1.0 Removed: \- Permission: \- Output: Examples: The replicas-all info command, using asadm ```bash Admin+> asinfo -v replicas-all 1.0.0.127.in-addr.arpa:3100 (127.0.0.1) returned: test:2,CQbAhIEKABVYgAWMS4gDxCkCBsEbIM8VLYwA3BLoULtgIBURK1NFKgUkLwMQKAkKgRmhVCUhgUFBqzAP4EKQEANAyMgcqBzAWtCpEOkIQMXRGACfyglogTCCpEslmRYwyYIB4TFTYSAQskRhIQA4ShE4UoeAPCMB3RUgOCkhMUTKCEhgBwBTAUhTtlwMUDEx66KmgooDo1AComhokkqasQIBHiOCPrA9zxg7AKkkQrIGCYSNc6CRwA8CAAtFyiTQCN4GIQivIwiKkfgRDAAChjgqwEgDCjEmACIQgQUzQpQMioSFUSDAJYBWVTsMSIaJHYCABDkAAdzZQ4lOYKrUC6TcwFhtyYywKMEIAKkZnAxDgFBE0DjiEBCJxkIeCIGCAEBjGFCQTSoGgAgCLkIQCwpYAwBMEEAJAyovCGGGhaCyPQQAITGSwma4EDVACQECdiGVClFUMoDRCIjiIB7hLdQTA0oRCTCyBBObwDASICVZQpwVFp5SYwAsBgRYCERw5iSUIEJBxoBUIYYAHtwI1IPVwgAIS8TMCsFhOUQA+EJOg2LQIQDCFyIBoYFCICUuAQVGSDoKvAIMTEpVJ4vM5GZQiIRBJ6ECMDEiTAsQBiBYsJI0ARgYXBLh+QDlzkFgMIwIkbKE60DkZAgIx9a//SKSJJRKJRJSJRRSSRJJRSI=dIASaQREXYqkBxACsGN8OAQo6CzgxTDo0BJOAc0AiwSRzGLIlAgYUNICEDCDxMIkJiRAAdqUfKgABIkQBx1A5jQ7BATjFSM6gSlEAxSCLgIOp5kgMNITGAF0C7DSYKmHNFTeGsakDBCpRLuUgGNBBagEJCheAcgiAkBWRVSKyLoUVAWVCF2s9pSASCMRAIrGEAUYPCB0DI3NAYYWQJBBAN3IABgEAQKAAGWAeABTGQQoVjFyBFAGP2DhjDCaAQgIcSARBjcAiMU0IAQMQcB8WIeVMqQ8NYRQtFWObKLMmEISVTtoKAAekBMJAoQBJUhioGEvo8BbTAIiBBIxGxUJNAkDE4cQFCECxBaxtEZmQDMQcAmpDYMZA0ACAImgkmpBN6iEpysLshCgTwX8wIiFdKCHGBsCqrOkCAHAN5opAlBIwhIM2MJtIYADzIA4IHbRAMAC4AYBDGomsAQI38AcAiogSCXEUoFNOSAgO81EhlimoUDAiECgiEUC+Himx6kJGUgIGBAuKRwqGCnKIQFlI0wqNazVJCogpBaUwotjAbiheIUBwo4QaNyiEgKdDkiBYIIpFsFkQuAwsaQoUCABEwApIzsAWAZ1C0YEEqAueBigRWnLWsfCoKAaAr8aMLgHxzI2CA0jEAAAAAAAGAFAABBBAyKFGImJSIopJIkyKJQ= 1.0.0.127.in-addr.arpa:3102 (127.0.0.1) returned: test:2,MjAOaR7g8GiHCEpxlHW4EUbdGQaAVxCCwCEKAKgWDQSWhYqoUCyyBWAL0JjAgPKELKYAi8iYTB6mQICQE71AK0CBJCTjV0IfhAdS5BSmKDguJscgMDKCFMQxAoDQAoAIEiE4HIaAABqPCBuYmJwGkYYBIVhvwgxCIECNhhZSwqExtyWagO8EIgOgCQCjjAxIFERREUGwCIFcFRaEACFkBvxCoUxAwU8CAGGAwBaaqAnhkhhQDBNOJFBdfBSqAUEMpyCIBLYA2KMQIgMi8eiJeMJEPDPUYUTR7lFuGFDADSkiYGhiqp8JiDoAKkAiBjgCgAds6AZ8rAEAmHIgH0UJcAAjGISCEgEIxCAixQJGQBIcJqyQIwQZxKM0EISBhCZcnr6MJqJgEMRhDeT1wIlptMQmUOKyB7h2OMUA8phoehNJgGorWoRhMAlDbUIEZkqQAFooMKCjyEAmZEYJCyAUggOAzAUqlsRFgYBgE4oAR9IChWPKQWAtGK3CsfADY5KBGNIAGgA2IGACyiltQAGXCQgAOB0VBAgTECqQgrNkBxkQUBwpEgg9oFFARGwhFACAViKBB8W0QG1RMZCgyBQRERCvZCq+mFQFwggBIYDJOMEgBkyApkNgoOwMAm0YECaFTECEAgQ6BIEbEfaFAAAAAkkkkkkkkkkkkkkkkkkkkkk=,gUnhlmEbAgBY8KGAAYgAxpkAAlEXKI8AI8CxbgIJMMIoEhEHK8NEgAnQBkYsMwxT0UGfZARigkAYE1ZjaEAvAIpEExMMiJyAINCJGENZkUUQUCDODw1EYzoKcAwtBFZwQAgAQRlI8sVAIUQCRwCgYkDS2AcAEBKc0aogEIAENQAKCNpAdwACCShfMphMY2AxQBqiwp4IcXIi6GEpvU4KyQA1XKI7CpB9uJJ1B0kEBGAQKMaB8aywQIcCA8kEfLLzAMFk2Ej4JRBBzWjBAhcCBxgiQUADggoMAagRgggDIITJgoSUVGBgQsT2wBHYkAEdXpiQEBCAE7xcYA3AgKrmgVKEJGghaVrVO8lECpmQu8DjCRJG0HgkOBzBaTBYYZEgQEFxWASETQEYsBoCGzQCChNQpARBUEQIxzAZAGSUgQw2OIXQBQmSjFQ8AgnDkIEsmQRBDxlYMRWICzn2AA3jUdBdMZoAIQoiQk+cxBC7GAAIGpg0NpNCZRIxAAcAGERmZgFjxe+AUoPVBFQQjqoAgDLVQEIi21HEScALNQSYSAYMBSKWLXGAFAAdKZEA4bdYiVxQqCIJPRCGCgETJssiaM8AkEQAJgmKNKD4wFYQhSZfuBAwADgVTxOh/QCAhUFYEAlBdWJAyz5AigFyICgAAIQISJRSRSRSJSSSSSSJRSI= 1.0.0.127.in-addr.arpa:3101 (127.0.0.1) returned: test:2,xMkxEmAVD4Igd7ACIAJEKpAg4DhkiCBoElL1I0UBokAJWmBGhIAI0JrQAGQvVwRxUkBeIBJGMqAYFE9gDAAvxLw+ExMAAKEgISgECwJRlwIAwThABcQVagtMWTQKZGnHJFzGAkgsnsVgRaAGRmPBJGjGjCAQAdC8AqpSQcCMDBoEQJIFeBCo3LQMQKNQI8KGABkIbDRMVC6hSIETbZQBSAG8QJA9AADAMIZEP0BBFUQYZGMigEwgG6Cgg+AQNJojUAFx2kFQBFRlTATMAhd0AQWRA4QolIoIEYyBZqoMsELRFRMYBEA2UkWpgITRsUF0YngTE8CDUiImJASRgBAihFsAJyMQJHJHEx7VOlSgI+GgWQMrDMMEK0xCKTlgc1ghYQEQwQ0PohGYchMIETSGQDGBrB0B6AeAxBDQBQYRAEwEQpHUhEoMDZAEgoi7kLRtiYRCxQ4IBT8IkzEU1MEKUChsMLDEYAsIemwELEXtmAikOAAgqAGAhFIRSAuklCkOAQlrxb2IGR+pFFCSoSJgInQqBeLisDMg5RQORAibAKShLIEGzPcASIy+GhKcy9pRqNg4sABBA5CigiUKEGAiCokAE1EAQAr4DcbcknQmwR6HSSFLWKSHAwESBJICIZgagzNzbElBED4AigFyOClAAJRJSSKRSKSJSKKJJKSSKJQ=,CjYMAJqgoHUDCE59ThSDAWLXFYIIEkAXDC0AkDD2RDlGIYwwQDSjLyQt6YlQCDGICJogmiEJARfn6CCMkKKQGUGA6OgQYkBFXgYy5KgkQLjhCEYRwCCohMSBhEMAmwAIi6MhpCATASoWmgBpOJwemBcpA9Ch7iVBLBWJqitxAkXhoyAqgKJRAEMghUSinBUIr+BFAUGDggAQFhjAAiG0NiICo0XA9G0CRwgKgLao4pvHgQgMCgNJgBgccAZhgkUEjh6KIYAHUiqKEpMyvCiBoGBIjBvASHGjSgJgEVUwRzkkKEADg5+BLSgAPWomSraAAQZATC8koEGBm+AOZEAQSqR4yBDOgoQoACAKQSAJBAwMhuQQIgTCxKM8lkYHDASeiBYKANBwAO5HAOABJEN4gUwoQ+C8BQhTMM4myAFCfKOBBWgjIjQAUivAMXYETwgCZju8EOCmwoBRRMIBIDIArAWChkA7jHSQhJBDACIAYadRRCcLQSwdEqjMB4BZIBKQgLaUIgBRhGAA44IlUFSaXIEAihEIAIQbEilgCHAEtkFSglhoEABvgyNAxGxiEAAmFiGGQRySgA9JRFrEiRTchDDWTID/gfAAwBkDLQnBAsEAAoYEpQAoEExEAEBlSgagKMSIgpCcJMG/df6Nx9a//2u2tEkoolIkklFEklJEkkk= ``` --- The output of \`show pmap\` in asadm ```bash Admin+> show pmap ~~~~~~~~~~~~~~~~~~~Partition Map Analysis (2024-11-26 22:16:09 UTC)~~~~~~~~~~~~~~~~~~ Namespace| Node| Cluster Key|~~~~~~~~~~~~Partitions~~~~~~~~~~~~ | | |Primary|Secondary|Unavailable|Dead test |1.0.0.127.in-addr.arpa:3100|5EA0F7252139| 1365| 1365| 0| 0 test |1.0.0.127.in-addr.arpa:3101|5EA0F7252139| 1365| 1366| 0| 0 test |1.0.0.127.in-addr.arpa:3102|5EA0F7252139| 1366| 1365| 0| 0 test | | | 4096| 4096| 0| 0 Number of rows: 3 ``` Related: [replicas](#replicas)[replicas-master](#replicas-master) --- #### `replicas-master` Command: ```bash replicas-master ``` Descriptions: Displays a bitmap of the master partitions. Use `asadm’s` `show pmap` instead, which gives the human-readable equivalent. Deprecated since Database 8.1.0 in favor of the `replicas` info command. Deprecated: 8.1.0 Removed: \- Permission: \- Output: Examples: The replicas-master info command, using asadm ```bash Admin+> asinfo -v replicas-master 1.0.0.127.in-addr.arpa:3100 (127.0.0.1) returned: test:CQbAhIEKABVYgAWMS4gDxCkCBsEbIM8VLYwA3BLoULtgIBURK1NFKgUkLwMQKAkKgRmhVCUhgUFBqzAP4EKQEANAyMgcqBzAWtCpEOkIQMXRGACfyglogTCCpEslmRYwyYIB4TFTYSAQskRhIQA4ShE4UoeAPCMB3RUgOCkhMUTKCEhgBwBTAUhTtlwMUDEx66KmgooDo1AComhokkqasQIBHiOCPrA9zxg7AKkkQrIGCYSNc6CRwA8CAAtFyiTQCN4GIQivIwiKkfgRDAAChjgqwEgDCjEmACIQgQUzQpQMioSFUSDAJYBWVTsMSIaJHYCABDkAAdzZQ4lOYKrUC6TcwFhtyYywKMEIAKkZnAxDgFBE0DjiEBCJxkIeCIGCAEBjGFCQTSoGgAgCLkIQCwpYAwBMEEAJAyovCGGGhaCyPQQAITGSwma4EDVACQECdiGVClFUMoDRCIjiIB7hLdQTA0oRCTCyBBObwDASICVZQpwVFp5SYwAsBgRYCERw5iSUIEJBxoBUIYYAHtwI1IPVwgAIS8TMCsFhOUQA+EJOg2LQIQDCFyIBoYFCICUuAQVGSDoKvAIMTEpVJ4vM5GZQiIRBJ6ECMDEiTAsQBiBYsJI0ARgYXBLh+QDlzkFgMIwIkbKE60DkZAgIx9a//SKSJJRKJRJSJRRSSRJJRSI 1.0.0.127.in-addr.arpa:3102 (127.0.0.1) returned: test:MjAOaR7g8GiHCEpxlHW4EUbdGQaAVxCCwCEKAKgWDQSWhYqoUCyyBWAL0JjAgPKELKYAi8iYTB6mQICQE71AK0CBJCTjV0IfhAdS5BSmKDguJscgMDKCFMQxAoDQAoAIEiE4HIaAABqPCBuYmJwGkYYBIVhvwgxCIECNhhZSwqExtyWagO8EIgOgCQCjjAxIFERREUGwCIFcFRaEACFkBvxCoUxAwU8CAGGAwBaaqAnhkhhQDBNOJFBdfBSqAUEMpyCIBLYA2KMQIgMi8eiJeMJEPDPUYUTR7lFuGFDADSkiYGhiqp8JiDoAKkAiBjgCgAds6AZ8rAEAmHIgH0UJcAAjGISCEgEIxCAixQJGQBIcJqyQIwQZxKM0EISBhCZcnr6MJqJgEMRhDeT1wIlptMQmUOKyB7h2OMUA8phoehNJgGorWoRhMAlDbUIEZkqQAFooMKCjyEAmZEYJCyAUggOAzAUqlsRFgYBgE4oAR9IChWPKQWAtGK3CsfADY5KBGNIAGgA2IGACyiltQAGXCQgAOB0VBAgTECqQgrNkBxkQUBwpEgg9oFFARGwhFACAViKBB8W0QG1RMZCgyBQRERCvZCq+mFQFwggBIYDJOMEgBkyApkNgoOwMAm0YECaFTECEAgQ6BIEbEfaFAAAAAkkkkkkkkkkkkkkkkkkkkkk= 1.0.0.127.in-addr.arpa:3101 (127.0.0.1) returned: test:xMkxEmAVD4Igd7ACIAJEKpAg4DhkiCBoElL1I0UBokAJWmBGhIAI0JrQAGQvVwRxUkBeIBJGMqAYFE9gDAAvxLw+ExMAAKEgISgECwJRlwIAwThABcQVagtMWTQKZGnHJFzGAkgsnsVgRaAGRmPBJGjGjCAQAdC8AqpSQcCMDBoEQJIFeBCo3LQMQKNQI8KGABkIbDRMVC6hSIETbZQBSAG8QJA9AADAMIZEP0BBFUQYZGMigEwgG6Cgg+AQNJojUAFx2kFQBFRlTATMAhd0AQWRA4QolIoIEYyBZqoMsELRFRMYBEA2UkWpgITRsUF0YngTE8CDUiImJASRgBAihFsAJyMQJHJHEx7VOlSgI+GgWQMrDMMEK0xCKTlgc1ghYQEQwQ0PohGYchMIETSGQDGBrB0B6AeAxBDQBQYRAEwEQpHUhEoMDZAEgoi7kLRtiYRCxQ4IBT8IkzEU1MEKUChsMLDEYAsIemwELEXtmAikOAAgqAGAhFIRSAuklCkOAQlrxb2IGR+pFFCSoSJgInQqBeLisDMg5RQORAibAKShLIEGzPcASIy+GhKcy9pRqNg4sABBA5CigiUKEGAiCokAE1EAQAr4DcbcknQmwR6HSSFLWKSHAwESBJICIZgagzNzbElBED4AigFyOClAAJRJSSKRSKSJSKKJJKSSKJQ= ``` --- The output of \`show pmap\` in asadm ```bash Admin+> show pmap ~~~~~~~~~~~~~~~~~~~Partition Map Analysis (2024-11-26 22:16:09 UTC)~~~~~~~~~~~~~~~~~~ Namespace| Node| Cluster Key|~~~~~~~~~~~~Partitions~~~~~~~~~~~~ | | |Primary|Secondary|Unavailable|Dead test |1.0.0.127.in-addr.arpa:3100|5EA0F7252139| 1365| 1365| 0| 0 test |1.0.0.127.in-addr.arpa:3101|5EA0F7252139| 1365| 1366| 0| 0 test |1.0.0.127.in-addr.arpa:3102|5EA0F7252139| 1366| 1365| 0| 0 test | | | 4096| 4096| 0| 0 Number of rows: 3 ``` Related: [replicas](#replicas)[replicas-all](#replicas-all) --- #### `replicas` Command: ```bash replicas ``` Descriptions: Displays a bitmap of the replica partitions. Use asadm’s `show pmap` instead, which gives the human-readable equivalent. Deprecated: \- Removed: \- Permission: \- Output: Examples: The replicas info command, using asadm ```bash Admin+> asinfo -v replicas 1.0.0.127.in-addr.arpa:3100 (127.0.0.1) returned: test:0,2,CQbAhIEKABVYgAWMS4gDxCkCBsEbIM8VLYwA3BLoULtgIBURK1NFKgUkLwMQKAkKgRmhVCUhgUFBqzAP4EKQEANAyMgcqBzAWtCpEOkIQMXRGACfyglogTCCpEslmRYwyYIB4TFTYSAQskRhIQA4ShE4UoeAPCMB3RUgOCkhMUTKCEhgBwBTAUhTtlwMUDEx66KmgooDo1AComhokkqasQIBHiOCPrA9zxg7AKkkQrIGCYSNc6CRwA8CAAtFyiTQCN4GIQivIwiKkfgRDAAChjgqwEgDCjEmACIQgQUzQpQMioSFUSDAJYBWVTsMSIaJHYCABDkAAdzZQ4lOYKrUC6TcwFhtyYywKMEIAKkZnAxDgFBE0DjiEBCJxkIeCIGCAEBjGFCQTSoGgAgCLkIQCwpYAwBMEEAJAyovCGGGhaCyPQQAITGSwma4EDVACQECdiGVClFUMoDRCIjiIB7hLdQTA0oRCTCyBBObwDASICVZQpwVFp5SYwAsBgRYCERw5iSUIEJBxoBUIYYAHtwI1IPVwgAIS8TMCsFhOUQA+EJOg2LQIQDCFyIBoYFCICUuAQVGSDoKvAIMTEpVJ4vM5GZQiIRBJ6ECMDEiTAsQBiBYsJI0ARgYXBLh+QDlzkFgMIwIkbKE60DkZAgIx9a//SKSJJRKJRJSJRRSSRJJRSI=,dIASaQREXYqkBxACsGN8OAQo6CzgxTDo0BJOAc0AiwSRzGLIlAgYUNICEDCDxMIkJiRAAdqUfKgABIkQBx1A5jQ7BATjFSM6gSlEAxSCLgIOp5kgMNITGAF0C7DSYKmHNFTeGsakDBCpRLuUgGNBBagEJCheAcgiAkBWRVSKyLoUVAWVCF2s9pSASCMRAIrGEAUYPCB0DI3NAYYWQJBBAN3IABgEAQKAAGWAeABTGQQoVjFyBFAGP2DhjDCaAQgIcSARBjcAiMU0IAQMQcB8WIeVMqQ8NYRQtFWObKLMmEISVTtoKAAekBMJAoQBJUhioGEvo8BbTAIiBBIxGxUJNAkDE4cQFCECxBaxtEZmQDMQcAmpDYMZA0ACAImgkmpBN6iEpysLshCgTwX8wIiFdKCHGBsCqrOkCAHAN5opAlBIwhIM2MJtIYADzIA4IHbRAMAC4AYBDGomsAQI38AcAiogSCXEUoFNOSAgO81EhlimoUDAiECgiEUC+Himx6kJGUgIGBAuKRwqGCnKIQFlI0wqNazVJCogpBaUwotjAbiheIUBwo4QaNyiEgKdDkiBYIIpFsFkQuAwsaQoUCABEwApIzsAWAZ1C0YEEqAueBigRWnLWsfCoKAaAr8aMLgHxzI2CA0jEAAAAAAAGAFAABBBAyKFGImJSIopJIkyKJQ= 1.0.0.127.in-addr.arpa:3102 (127.0.0.1) returned: test:0,2,MjAOaR7g8GiHCEpxlHW4EUbdGQaAVxCCwCEKAKgWDQSWhYqoUCyyBWAL0JjAgPKELKYAi8iYTB6mQICQE71AK0CBJCTjV0IfhAdS5BSmKDguJscgMDKCFMQxAoDQAoAIEiE4HIaAABqPCBuYmJwGkYYBIVhvwgxCIECNhhZSwqExtyWagO8EIgOgCQCjjAxIFERREUGwCIFcFRaEACFkBvxCoUxAwU8CAGGAwBaaqAnhkhhQDBNOJFBdfBSqAUEMpyCIBLYA2KMQIgMi8eiJeMJEPDPUYUTR7lFuGFDADSkiYGhiqp8JiDoAKkAiBjgCgAds6AZ8rAEAmHIgH0UJcAAjGISCEgEIxCAixQJGQBIcJqyQIwQZxKM0EISBhCZcnr6MJqJgEMRhDeT1wIlptMQmUOKyB7h2OMUA8phoehNJgGorWoRhMAlDbUIEZkqQAFooMKCjyEAmZEYJCyAUggOAzAUqlsRFgYBgE4oAR9IChWPKQWAtGK3CsfADY5KBGNIAGgA2IGACyiltQAGXCQgAOB0VBAgTECqQgrNkBxkQUBwpEgg9oFFARGwhFACAViKBB8W0QG1RMZCgyBQRERCvZCq+mFQFwggBIYDJOMEgBkyApkNgoOwMAm0YECaFTECEAgQ6BIEbEfaFAAAAAkkkkkkkkkkkkkkkkkkkkkk=,gUnhlmEbAgBY8KGAAYgAxpkAAlEXKI8AI8CxbgIJMMIoEhEHK8NEgAnQBkYsMwxT0UGfZARigkAYE1ZjaEAvAIpEExMMiJyAINCJGENZkUUQUCDODw1EYzoKcAwtBFZwQAgAQRlI8sVAIUQCRwCgYkDS2AcAEBKc0aogEIAENQAKCNpAdwACCShfMphMY2AxQBqiwp4IcXIi6GEpvU4KyQA1XKI7CpB9uJJ1B0kEBGAQKMaB8aywQIcCA8kEfLLzAMFk2Ej4JRBBzWjBAhcCBxgiQUADggoMAagRgggDIITJgoSUVGBgQsT2wBHYkAEdXpiQEBCAE7xcYA3AgKrmgVKEJGghaVrVO8lECpmQu8DjCRJG0HgkOBzBaTBYYZEgQEFxWASETQEYsBoCGzQCChNQpARBUEQIxzAZAGSUgQw2OIXQBQmSjFQ8AgnDkIEsmQRBDxlYMRWICzn2AA3jUdBdMZoAIQoiQk+cxBC7GAAIGpg0NpNCZRIxAAcAGERmZgFjxe+AUoPVBFQQjqoAgDLVQEIi21HEScALNQSYSAYMBSKWLXGAFAAdKZEA4bdYiVxQqCIJPRCGCgETJssiaM8AkEQAJgmKNKD4wFYQhSZfuBAwADgVTxOh/QCAhUFYEAlBdWJAyz5AigFyICgAAIQISJRSRSRSJSSSSSSJRSI= 1.0.0.127.in-addr.arpa:3101 (127.0.0.1) returned: test:0,2,xMkxEmAVD4Igd7ACIAJEKpAg4DhkiCBoElL1I0UBokAJWmBGhIAI0JrQAGQvVwRxUkBeIBJGMqAYFE9gDAAvxLw+ExMAAKEgISgECwJRlwIAwThABcQVagtMWTQKZGnHJFzGAkgsnsVgRaAGRmPBJGjGjCAQAdC8AqpSQcCMDBoEQJIFeBCo3LQMQKNQI8KGABkIbDRMVC6hSIETbZQBSAG8QJA9AADAMIZEP0BBFUQYZGMigEwgG6Cgg+AQNJojUAFx2kFQBFRlTATMAhd0AQWRA4QolIoIEYyBZqoMsELRFRMYBEA2UkWpgITRsUF0YngTE8CDUiImJASRgBAihFsAJyMQJHJHEx7VOlSgI+GgWQMrDMMEK0xCKTlgc1ghYQEQwQ0PohGYchMIETSGQDGBrB0B6AeAxBDQBQYRAEwEQpHUhEoMDZAEgoi7kLRtiYRCxQ4IBT8IkzEU1MEKUChsMLDEYAsIemwELEXtmAikOAAgqAGAhFIRSAuklCkOAQlrxb2IGR+pFFCSoSJgInQqBeLisDMg5RQORAibAKShLIEGzPcASIy+GhKcy9pRqNg4sABBA5CigiUKEGAiCokAE1EAQAr4DcbcknQmwR6HSSFLWKSHAwESBJICIZgagzNzbElBED4AigFyOClAAJRJSSKRSKSJSKKJJKSSKJQ=,CjYMAJqgoHUDCE59ThSDAWLXFYIIEkAXDC0AkDD2RDlGIYwwQDSjLyQt6YlQCDGICJogmiEJARfn6CCMkKKQGUGA6OgQYkBFXgYy5KgkQLjhCEYRwCCohMSBhEMAmwAIi6MhpCATASoWmgBpOJwemBcpA9Ch7iVBLBWJqitxAkXhoyAqgKJRAEMghUSinBUIr+BFAUGDggAQFhjAAiG0NiICo0XA9G0CRwgKgLao4pvHgQgMCgNJgBgccAZhgkUEjh6KIYAHUiqKEpMyvCiBoGBIjBvASHGjSgJgEVUwRzkkKEADg5+BLSgAPWomSraAAQZATC8koEGBm+AOZEAQSqR4yBDOgoQoACAKQSAJBAwMhuQQIgTCxKM8lkYHDASeiBYKANBwAO5HAOABJEN4gUwoQ+C8BQhTMM4myAFCfKOBBWgjIjQAUivAMXYETwgCZju8EOCmwoBRRMIBIDIArAWChkA7jHSQhJBDACIAYadRRCcLQSwdEqjMB4BZIBKQgLaUIgBRhGAA44IlUFSaXIEAihEIAIQbEilgCHAEtkFSglhoEABvgyNAxGxiEAAmFiGGQRySgA9JRFrEiRTchDDWTID/gfAAwBkDLQnBAsEAAoYEpQAoEExEAEBlSgagKMSIgpCcJMG/df6Nx9a//2u2tEkoolIkklFEklJEkkk= ``` --- The output of \`show pmap\` in asadm ```bash Admin+> show pmap ~~~~~~~~~~~~~~~~~~~Partition Map Analysis (2024-11-26 22:16:09 UTC)~~~~~~~~~~~~~~~~~~ Namespace| Node| Cluster Key|~~~~~~~~~~~~Partitions~~~~~~~~~~~~ | | |Primary|Secondary|Unavailable|Dead test |1.0.0.127.in-addr.arpa:3100|5EA0F7252139| 1365| 1365| 0| 0 test |1.0.0.127.in-addr.arpa:3101|5EA0F7252139| 1365| 1366| 0| 0 test |1.0.0.127.in-addr.arpa:3102|5EA0F7252139| 1366| 1365| 0| 0 test | | | 4096| 4096| 0| 0 Number of rows: 3 ``` Related: [replicas-all](#replicas-all)[replicas-master](#replicas-master) --- #### `revive` Command: ```bash revive:namespace=NAMESPACE_NAME ``` Descriptions: Used to revive dead partitions in a namespace running in strong consistency mode. Should be followed by the recluster command in order to take effect. Revived nodes restore availability only when all nodes are trusted. Introduced: 4.0.0 Deprecated: \- Removed: \- Permission: sys-admin Output: On success returns OK. Examples: Execute Command ```bash Admin+> asinfo -v 'revive:namespace=test' 192.168.100.233:3000 (192.168.100.233) returned: ok 192.168.100.215:3000 (192.168.100.215) returned: ok ``` Related: [recluster](#recluster) --- #### `roster-set` Command: ```bash roster-set:namespace=NAMESPACE_NAME;nodes=OBSERVED_NODES_LIST ``` Descriptions: Set the roster (for namespaces running in strong consistency mode). Requires ‘recluster’ to take effect. For removing a node from the roster, follow the [Removing Nodes](https://aerospike.com/docs/database/manage/cluster/consistency/#remove-node-from-the-roster) paragraph of the [Manage Consistency](https://aerospike.com/docs/database/manage/cluster/consistency) documentation page. The equivalent command in asadm is [`manage roster`](https://aerospike.com/docs/database/tools/asadm/live-mode#roster-1).You can also use `manage roster stage observed`. Introduced: 4.0.0 Deprecated: \- Removed: \- Permission: sys-admin Output: Set the roster for the namespace. It is safe to issue this command multiple times, once for each observed node, or create a list, but issuing it for against one node is enough (command is propagated through SMD). The roster is not active until the recluster command is issued. Validate the roster prior to issuing the recluster command by running the roster command and verifying all desired roster nodes are in the pending\_roster list. Examples: Execute Command ```bash Admin+> asinfo -v "roster-set:namespace=test;nodes=BB9070016AE4202,BB9060016AE4202,BB9050016AE4202, BB9040016AE4202,BB9020016AE4202" with BB9020016AE4202 node1.aerospike.com:3000 (192.168.10.10) returned: ok ``` Related: [roster](#roster)[recluster](#recluster) --- #### `roster` Command: ```bash roster:namespace=NAMESPACE_NAME ``` Descriptions: Show roster information (for namespaces running in strong consistency mode). The equivalent command in asadm is [`show roster`](https://aerospike.com/docs/database/tools/asadm/live-mode#roster). Introduced: 4.0.0 Deprecated: \- Removed: \- Permission: \- Output: Returns the list of node currently in the roster. Examples: Execute Command ```bash Admin+> asinfo -v "roster:namespace=test" node1.aerospike.com:3000 (192.168.10.10) returned: roster=null:pending_roster=null:observed_nodes=BB9070016AE4202,BB9060016AE4202,BB9050016AE4202,BB9040016AE4202,BB9020016AE4202 node2.aerospike.com:3000 (192.168.10.11) returned: roster=null:pending_roster=null:observed_nodes=BB9070016AE4202,BB9060016AE4202,BB9050016AE4202,BB9040016AE4202,BB9020016AE4202 node3.aerospike.com:3000 (192.168.10.12) returned: roster=null:pending_roster=null:observed_nodes=BB9070016AE4202,BB9060016AE4202,BB9050016AE4202,BB9040016AE4202,BB9020016AE4202 node4.aerospike.com:3000 (192.168.10.13) returned: roster=null:pending_roster=null:observed_nodes=BB9070016AE4202,BB9060016AE4202,BB9050016AE4202,BB9040016AE4202,BB9020016AE4202 node5.aerospike.com:3000 (192.168.10.14) returned: roster=null:pending_roster=null:observed_nodes=BB9070016AE4202,BB9060016AE4202,BB9050016AE4202,BB9040016AE4202,BB9020016AE4202 node6.aerospike.com:3000 (192.168.10.15) returned: roster=null:pending_roster=null:observed_nodes=BB9070016AE4202,BB9060016AE4202,BB9050016AE4202,BB9040016AE4202,BB9020016AE4202 ``` Related: [roster-set](#roster-set) --- #### `scan-abort-all` Command: ```bash scan-abort-all: ``` Descriptions: Abort all scans running on the server node, across all namespaces. This info command was deprecated in Database 6.0.0, and removed in Database 6.4.0. Use `query-abort-all` instead. Introduced: 3.5.12 Deprecated: \- Removed: 6.4.0 Permission: data-admin Output: Returns “OK - number of scans killed: x” where x is the number of aborted scans. Examples: Abort all scans ```bash asinfo -v 'scan-abort-all:' OK - number of scans killed: 7 ``` Related: [scan-abort](#scan-abort)[scan-show](#scan-show) --- #### `scan-abort` Command: ```bash scan-abort:id=TRANSACTIONID ``` Descriptions: Abort a scan running on the server node. This info command was deprecated in Database 6.0.0, and removed in Database 6.4.0. Use `query-abort` instead. Introduced: 3.3.0 Deprecated: \- Removed: 6.4.0 Permission: data-admin Parameters: id Transaction ID to identify the scan to abort. This parameter is required. Output: Returns “OK” if the scan was aborted, otherwise a “Transaction Not Found” error. Examples: Abort a scan ```bash asinfo -v 'scan-abort:trid=1225169085971291877' OK ``` Related: [scan-abort-all](#scan-abort-all)[scan-show](#scan-show) --- #### `scan-show` Command: ```bash scan-show scan-show:trid=TRANSACTIONID ``` Descriptions: Returns information about current/recent scans on the server node. This info command was deprecated in Database 6.0.0, and removed in Database 6.4.0. Use `query-show` instead. The equivalent command in asadm is [`show jobs scans`](https://aerospike.com/docs/database/tools/asadm/live-mode#jobs). Introduced: 5.7.0 Deprecated: \- Removed: 6.4.0 Permission: \- Parameters: trid Transaction ID to specify a particular scan. If this parameter is omitted, information is returned about every running scan, as well as all completed scans, up to the limit specified by [`query-max-done`](https://aerospike.com/docs/database/reference/config#service__query-max-done) Output: Scan Information Scan information includes: - trid - transaction ID of the scan - job-type - type of scan, one of: - basic - aggregation - background-udf - background-ops - ns - name of scanned namespace - set - name of scanned set (only appears if scan specifies a set) - n-pids-requested - number of partitions requested for the scan (only appears if nonzero) - rps - scan rate (records per second) requested for the scan - active-threads - number of threads currently processing the scan - status - scan status, one of: - active(ok) - in progress - done(ok) - completed successfully - done(user-aborted) - aborted by user - done(abandoned-unknown) - abandoned with unknown failure - done(abandoned-response-error) - aborted due to error responding to client - done(abandoned-response-timeout) - aborted due to timeout responding to client - job-progress - estimated scan completion percentage - run-time - how long the scan has taken (or how long it took), in milliseconds - time-since-done - how long ago the scan finished, in milliseconds - recs-throttled - number of records examined by the scan for throttling purposes. Those are records that are read but may or may not be returned. - recs-filtered-meta - number of records filtered out by an [expression](https://aerospike.com/docs/develop/expressions) at the metadata level - recs-filtered-bins - number of records filtered out by an [expression](https://aerospike.com/docs/develop/expressions) at the bin level - recs-succeeded - number of records successfully processed by the scan - recs-failed - number of records that failed processing (e.g. unreadable) - net-io-bytes - amount of response data sent, in bytes - net-io-time - time taken to send response data, in milliseconds - socket-timeout - socket timeout for the scan, in milliseconds - from - source of the scan request, in ip-address+port format - udf-filename - name of the UDF source file (background-udf scans only) - udf-function - name of the UDF function (background-udf scans only) - udf-active - number of active UDF transactions (background-udf scans only) - ops-active - number of active background ops transactions (background-ops scans only) Examples: Get information about all scans ```bash asinfo -v 'scan-show' -l module=query:trid=7283069042041732041:job-type=basic:ns=test:set=query_foreach:n-pids-requested=4096:\ rps=0:active-threads=0:status=done(ok):job-progress=100.00:run-time=1:time-since-done=17023:recs-throttled=0:\ recs-filtered-meta=0:recs-filtered-bins=1:recs-succeeded=5:recs-failed=0:net-io-bytes=90726:net-io-time=0:\ socket-timeout=30000:from=127.0.0.1+57202 ``` --- Get information about one scan ```bash asinfo -v 'scan-show:trid=2389620674112568291' -l trid=2389620674112568291 job-type=basic ns=test set=sb_test5 priority=0 n-pids-requested=4096 rps=0 active-threads=0 status=done(ok) job-progress=100.00 run-time=48 time-since-done=23231 recs-throttled=50 recs-filtered-meta=0 recs-filtered-bins=40 recs-succeeded=10 recs-failed=0 net-io-bytes=157488 socket-timeout=30000 from=127.0.0.1+50458 ``` Related: [scan-abort](#scan-abort)[scan-abort-all](#scan-abort-all)[query-show](#query-show) --- #### `service-clear-alt` Command: ```bash service-clear-alt ``` Descriptions: Supersedes “service” info command. The alternate address and port for this node’s non-TLS client service. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Examples: Execute Command ```bash asinfo -v "service-clear-alt" 74.125.239.52:3000 ``` Related: [peers-clear-alt](#peers-clear-alt)[peers-clear-std](#peers-clear-std)[peers-tls-alt](#peers-tls-alt)[peers-tls-std](#peers-tls-std)[service-clear-std](#service-clear-std)[service-tls-alt](#service-tls-alt)[service-tls-std](#service-tls-std) --- #### `service-clear-std` Command: ```bash service-clear-std ``` Descriptions: Supersedes “service” info command. The address and port for this node’s non-TLS client service. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Examples: Execute Command ```bash asinfo -v 'service-clear-std' 172.17.0.3:3000 ``` Related: [peers-clear-alt](#peers-clear-alt)[peers-clear-std](#peers-clear-std)[peers-tls-alt](#peers-tls-alt)[peers-tls-std](#peers-tls-std)[service-clear-alt](#service-clear-alt)[service-tls-alt](#service-tls-alt)[service-tls-std](#service-tls-std) --- #### `service-tls-alt` Command: ```bash service-tls-alt ``` Descriptions: Supersedes “service” info command. The alternate address and port for this node’s TLS client service. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Examples: Execute Command ```bash asinfo -v "service-tls-alt" 74.125.239.52:4333 ``` Related: [peers-clear-alt](#peers-clear-alt)[peers-clear-std](#peers-clear-std)[peers-tls-alt](#peers-tls-alt)[peers-tls-std](#peers-tls-std)[service-clear-alt](#service-clear-alt)[service-clear-std](#service-clear-std)[service-tls-std](#service-tls-std) --- #### `service-tls-std` Command: ```bash service-tls-std ``` Descriptions: Supersedes “service” info command. The address and port for this node’s TLS client service. Introduced: 3.11.0 Deprecated: \- Removed: \- Permission: \- Examples: Execute Command ```bash asinfo -v "service-tls-std" 172.17.0.3:4333 ``` Related: [peers-clear-alt](#peers-clear-alt)[peers-clear-std](#peers-clear-std)[peers-tls-alt](#peers-tls-alt)[peers-tls-std](#peers-tls-std)[service-clear-alt](#service-clear-alt)[service-clear-std](#service-clear-std)[service-tls-alt](#service-tls-alt) --- #### `service` Command: ```bash service ``` Descriptions: Deprecated in Database 8.1.0. Use [`service-clear-std`](https://aerospike.com/docs/database/reference/info/#service-clear-std) instead. IP address and server port for this node, expected to be a single address/port per node, may be multiple address if this node is configured to listen on multiple interfaces (typically not advised). Introduced: 3.3.0 Deprecated: 8.1.0 Removed: \- Permission: \- Output: Returns a list of IP:SERVICE\_PORT to be advertised to other cluster nodes. Typically considered a configuration issue if the list contains more than one IP. Examples: Execute Command ```bash asinfo -v 'service' 172.16.121.138:3000 ``` Related: [services](#services)[services-alternate](#services-alternate)[services-alumni](#services-alumni)[services-alumni-reset](#services-alumni-reset) --- #### `services-alternate` Command: ```bash services-alternate ``` Descriptions: Deprecated in Database 8.1.0. Use [`peers-clear-alt`](https://aerospike.com/docs/database/reference/info/#peers-clear-alt) instead. List of alternate service addresses of peer nodes. Introduced: 3.7.1 Deprecated: 8.1.0 Removed: \- Permission: \- Output: Returns a list of alternate neighboring IP:SERVICE\_PORT that are considered alive by this server and configured as alternate-access-address in the service stanza. Examples: Execute Command ```bash asinfo -v 'services-alternate' 192.168.120.145:3000;192.168.120.144:3000;192.168.120.143:3000;192.168.120.142:3000 ``` Related: [service](#service)[services](#services)[services-alumni](#services-alumni)[services-alumni-reset](#services-alumni-reset) --- #### `services-alumni-reset` Command: ```bash services-alumni-reset ``` Descriptions: Resets the neighbor addresses (services) the server should know about. Some diagnostic tools, eg. asadm, use alumni to enable full cluster view even during cluster disruptions. This command is useful if the alumni’s list includes servers which have been decommissioned. Introduced: 3.6.2 Deprecated: \- Removed: \- Permission: sys-admin Output: Returns OK after the refresh is completed. Examples: Execute Command ```bash asinfo -v 'services-alumni-reset' Ok ``` Related: [service](#service)[services](#services)[services-alumni](#services-alumni) --- #### `services-alumni` Command: ```bash services-alumni ``` Descriptions: Deprecated in Database 8.1.0. Use [`alumni-clear-std`](https://aerospike.com/docs/database/reference/info/#alumni-clear-std) instead. All neighbor addresses (services) this server has ever known about. Some diagnostic tools, eg. asadm, use alumni to enable full cluster view even during cluster disruptions. Introduced: 3.3.0 Deprecated: 8.1.0 Removed: \- Permission: \- Output: Returns a list of all neighboring IP:SERVICE\_PORT this node has ever known, including neighbor nodes this server believes to be Dead. Examples: Execute Command ```bash asinfo -v 'services-alumni' 192.168.120.145:3000;192.168.120.144:3000;192.168.120.143:3000;192.168.120.142:3000 ``` Related: [service](#service)[services](#services)[services-alternate](#services-alternate)[services-alumni-reset](#services-alumni-reset) --- #### `services` Command: ```bash services ``` Descriptions: Deprecated in Database 8.1.0. Use [`peers-clear-std`](https://aerospike.com/docs/database/reference/info/#peers-clear-std) instead. List of addresses of neighbor cluster nodes to advertise for Application to connect. Introduced: 3.3.0 Deprecated: 8.1.0 Removed: \- Permission: \- Output: Returns a list of neighboring IP:SERVICE\_PORT that are considered Alive by this server. Examples: Execute Command ```bash asinfo -v 'services' 192.168.120.145:3000;192.168.120.144:3000;192.168.120.143:3000 ``` Related: [service](#service)[services-alternate](#services-alternate)[services-alumni](#services-alumni)[services-alumni-reset](#services-alumni-reset) --- #### `set-config` Command: ```bash set-config:context=CONTEXT;PARAM=VALUE set-config:context=namespace;namespace=NAMESPACE_NAME;PARAM=VALUE ``` Descriptions: Set a configuration parameter at run time. The configuration parameter must be dynamic. The equivalent command in asadm is [`manage config`](https://aerospike.com/docs/database/tools/asadm/live-mode/#manage). Starting with Database 7.2.0, the `set-config` info command takes an alternative argument pair to designate a configuration inside a namespace section, `namespace=NS` and `id=NS`. However, `id=NS` is deprecated in Database 7.2.0. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: sys-admin Parameters: context Configuration context of where the parameter resides in the configuration file. Options: - namespace - network - service - xdr --- id Used for namespace contexts only. Name of the namespace where the configuration parameter resides. Output: Upon success command returns “ok” Examples: For Aerospike Database 5.0.0+ XDR, define a remote datacenter. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ action=create" ``` --- For Aerospike Database 5.0.0+ XDR, delete a remote datacenter. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ action=delete" ``` --- For Aerospike Database 5.0.0+ XDR, add a namespace. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ namespace=test;action=add" ``` --- For Aerospike Database 5.0.0+ XDR, remove a namespace. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ namespace=test;action=remove" ``` --- For Aerospike Database 5.0.0+ XDR, add or remove a node IP address/port combination to a remote datacenter. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ node-address-port=10.0.0.1:3000;action=add" ``` --- For Aerospike Database 5.0.0+ XDR, set configuration for a namespace. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ namespace=test;ship-only-specified-sets=true;ship-set=set1" ``` --- For Aerospike Database 5.0.0+ XDR, rewind the shipment of records back a specific number of seconds with \`rewind=numberOfSeconds\`.
For small datasets, you can restart the shipment entirely from the beginning with \`rewind=all\`. For large datasets, be careful with starting a complete rewind. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ namespace=test;action=add;rewind=600" ``` --- For Aerospike Database 5.0.0+ XDR, set an \`auth-user\` who has read/write privileges on the remote datacenter. The \`auth-user\` parameter must be accompanied by the \`auth-password-file\` parameter and should be set only when the datacenter is not connected; otherwise, login at the remote datacenter will continually fail. ```bash asinfo -h localhost -v "set-config:context=xdr;dc=aerospike_b;\ namespace=test;auth-user=someUser;auth-password-file=/private/security-credentials_DC1.txt" ``` --- Set \`heartbeat.timeout\` to 10 for network context ```bash asinfo -v 'set-config:context=network;heartbeat.timeout=10' ok ``` Related: [get-config](#get-config)[namespace](#namespace) --- #### `sets` Command: ```bash sets sets/NAMESPACE sets/NAMESPACE/SET ``` Descriptions: Returns set statistics for all or a particular set. Includes in-memory size of a set (if data-in-memory). Returns data for individual node unless run using `asadm`. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: NAMESPACE Namespace name to query set statistics from. --- SET Set name to query set statistics from. Output: Stats - ns - namespace name - set - set name - objects - master, replica and non-replica (during migrations) objects count. - tombstones - master, replica and non-replica (during migrations) tombstones count. - memory\_data\_bytes - memory used by master, replica and non-replica data (during migrations), excluding primary index. - device\_data\_bytes - device storage used by master, replica and non-replica (during migrations) data, excluding primary index (Database 5.2.0+). - enable-index - true/false - reflects if this set is indexed by a set index. (Database 5.6.0+). - index\_populating - true/false if the set is currently being indexed for its set index. (Database 5.6.0+). - sindexes - number of secondary indexes on this set. - truncating - true/false if this set is currently being truncated. (Database 6.3.0+). - truncate\_lut - The LUT (last updated time) in milliseconds since the Citrusleaf epoch (00:00:00 UTC on 1 Jan 2010). - stop-writes-count - value configured in [stop-writes-count](https://aerospike.com/docs/database/reference/config#namespace__stop-writes-count). - stop-writes-size - value configured in [stop-writes-size](https://aerospike.com/docs/database/reference/config#namespace__stop-writes-size). - disable-eviction - value configured in [disable-eviction.](https://aerospike.com/docs/database/reference/config#namespace__disable-eviction) Examples: Query set stats from all namespaces ```bash asinfo -v 'sets' -l ns=test:set=demo:objects=12345:tombstones=0:memory_data_bytes=851805:device_data_bytes=852400:truncate_lut=0:stop-writes-count=0:set-enable-xdr=use-default:sindexes=0:enable-index=false:index_populating=false:truncating=false:disable-eviction=true; ``` --- Query set stats from namespace 'test' ```bash asinfo -v 'sets/test' -l ns=test:set=demo:objects=1:tombstones=0:memory_data_bytes=0:device_data_bytes=40:truncate_lut=0:stop-writes-count=0:set-enable-xdr=use-default:sindexes=0:enable-index=false:index_populating=false:truncating=false:disable-eviction=true; ``` --- Query set stats from 'demo' set in namespace 'test' ```bash asinfo -v 'sets/test/demo' -l objects=1:tombstones=0:memory_data_bytes=0:device_data_bytes=40:truncate_lut=0:stop-writes-count=0:set-enable-xdr=use-default::sindexes=0:enable-index=false:index_populating=false:truncating=false:disable-eviction=true; ``` Related: [bins](#bins)[namespace](#namespace)[namespaces](#namespaces)[statistics](#statistics) --- #### `sindex-create` Command: ```bash # create a secondary index on a bin sindex-create:namespace=NAMESPACE[;set=SET];indexname=INDEX_NAME[;indextype=INDEX_TYPE];bin=BIN_NAME;type=BIN_TYPE[;context=] # create a secondary index on an expression sindex-create:namespace=NAMESPACE[;set=SET];indexname=INDEX_NAME[;indextype=INDEX_TYPE];exp=;type=BIN_TYPE ``` Descriptions: Create a secondary index. Database 8.1.0 and later support expression indexes. The parameter `indexdata=BIN_NAME,BIN_TYPE` format is deprecated. Introduced: 3.3.0 Deprecated: indexdata in 8.1.0 Removed: \- Permission: sindex-admin Parameters: namespace The namespace to create the secondary index on. Using `ns=NAMESPACE` as an alternative has been deprecated since Database 7.2.0. --- set (Optional) A set within the specified namespace to create a secondary index on. Starting with Database 6.1.0, omitting the `set` parameter means that the index applies to the entire namespace. In earlier versions, omitting the `set` parameter means that the index applies to all items in the namespace that are not a member of any set. --- indexname Canonical name for the newly-created secondary index. Name should be 63 characters or fewer. The colon `:` and semicolon `;` characters are not allowed in index names. --- indexdata Deprecated in Database 8.1.0, use `bin` and `type` instead. Tuple of the form `BIN_NAME,BIN_TYPE`. `BIN_NAME` is the name of the bin to create a secondary index on. `BIN_TYPE` is the bin type for the provided `BIN_NAME`. Options: `NUMERIC` `STRING` `GEO2DSPHERE` --- indextype (Optional) Specifies how the secondary index is to collect keys. Options: `default` Treat the value of the bin as a key. `list` Use the elements of a list as keys. `mapkeys` Use the keys of a map as keys. `mapvalues` Use the values of a map as keys. --- context (Optional) Specifies a base64-encoded context for indexing a value nested in a [List](https://aerospike.com/docs/develop/data-types/collections/list) or [Map](https://aerospike.com/docs/develop/data-types/collections/map) Collection Data Type (CDT). Output: On success returns `ok`. On failure returns an error message. Examples: Create a secondary index on an integer value ```bash asinfo -v 'sindex-create:indexname=dnr-age-idx;namespace=test;set=donor;bin=age;type=numeric;indextype=default' ``` --- Create a secondary index on a list of string values nested in a list bin called 'report' ```bash asinfo -v 'sindex-create:namespace=sandbox;set=ufodata;indexname=shape-idx;bin=report;type=string;indextype=list;context=kiKmA3NoYXBl' ``` --- Create a secondary index on an expression ```bash asinfo -v 'sindex-create:namespace=test;set=donor;indexname=dnr-sum-idx;indextype=default;exp=lBSTUQKpY2FtcGFpZ24xk1ECqWNhbXBhaWduMpNRAqljYW1wYWlnbjM=' ``` --- Deprecated format for creating a bin index, same as the one on 'report' above ```bash asinfo -v 'sindex-create:namespace=sandbox;set=ufodata;indexname=shape-idx;indexdata=report,string;indextype=list;context=kiKmA3NoYXBl' ``` Related: [sindex](#sindex)[sindex-list](#sindex-list)[sindex-delete](#sindex-delete)[sindex-stat](#sindex-stat) --- #### `sindex-delete` Command: ```bash sindex-delete:namespace=NAMESPACE_NAME[;set=SET];indexname=INDEX_NAME ``` Descriptions: Delete a secondary index. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: sindex-admin Parameters: namespace Namespace name where the target secondary index resides. `ns=NAMESPACE_NAME` is deprecated since Database 7.2.0. --- set (Optional) Name of the set where targeted by this secondary index. --- indexname Name of the secondary index to delete. Output: On success returns “ok”, otherwise returns an error message. Examples: Delete a secondary index. ```bash asinfo -v 'sindex-delete:namespace=test;indexname=demo-index' ok ``` Related: [sindex](#sindex)[sindex-create](#sindex-create)[sindex-list](#sindex-list)[sindex-histogram](#sindex-histogram) --- #### `sindex-histogram` Command: ```bash sindex-histogram:namespace=NAMESPACE_NAME;[set=SET];indexname=INDEX;enable=ENABLE ``` Descriptions: Enables query histograms to be printed in system logs of the target server. Introduced: 3.3.0 Deprecated: \- Removed: 6.0.0 Permission: sys-admin Parameters: ns Namespace name where the target secondary index resides. --- set (optional) Name of the Set where the target secondary index resides. --- indexname Name of the index to enable/disable histograms for. --- enable Can be either `true` or `false`. If `true` histograms are enabled for the provided index name. If `false` histograms are disabled for the provided index name. Output: On success returns “ok”, otherwise returns an error message. Examples: Enable Query Histograms to be Printed to the Logs ```bash asinfo -v 'sindex-histogram:namespace=test;set=demo;indexname=demo-index;enable=true' ok ``` --- Disable Query Histograms to be Printed to the Logs ```bash asinfo -v 'sindex-histogram:namespace=test;set=demo;indexname=demo-index;enable=false' ok ``` Related: [sindex](#sindex)[sindex-create](#sindex-create)[sindex-delete](#sindex-delete) --- #### `sindex-list` Command: ```bash sindex-list:namespace=NAMESPACE_NAME;b64=b64_FLAG ``` Descriptions: List secondary indexes. Starting with Database 6.1.0, you can specify whether to view the optional context in its base64-encoded representation. This command supplants the `sindex[/NAMESPACE]` command, which cannot accept non positional arguments. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: namespace Namespace name (optional) where the target secondary indexes reside. If not specified, list sindexes in all namespaces. `ns=NAMESPACE_NAME` is deprecated since Database 7.2.0. --- b64 (optional) false or true. Retrieve base64 encoding of the context of the secondary index. This can be used in other info commands, such as `sindex-create`. Otherwise it returns a human readable context (for bin indexes with a CDT context) or expression (for expression indexes) Output: On success returns “ok”, otherwise returns an error message. Examples: List secondary indexes in all namespaces: ```bash asinfo -v 'sindex-list:' ``` --- List secondary indexes in a specific namespace: ```bash asinfo -v 'sindex-list:namespace=test' ``` --- Nested CDT index example using base64 option; context and expression given in human-readable format: ```bash asinfo -v 'sindex-list:namespace=test;b64=false' -l ns=test:indexname=dnr-sum-idx:set=donor:bin=null:type=numeric:indextype=default:context=null:exp=add(bin_int("campaign1"), bin_int("campaign2"), bin_int("campaign3")):state=RW ns=test:indexname=dnr-zip-idx:set=donor:bin=address:type=numeric:indextype=default:context=[map_key()]:exp=null:state=RW ns=test:indexname=dnr-age-idx:set=donor:bin=age:type=numeric:indextype=default:context=null:exp=null:state=RW ``` --- Nested CDT index example using base64 option; presents context and expression used in the index as base64-encoded strings: ```bash asinfo -v 'sindex-list:namespace=test;b64=true' -l ns=test:indexname=dnr-sum-idx:set=donor:bin=null:type=numeric:indextype=default:context=null:exp=lBSTUQKpY2FtcGFpZ24xk1ECqWNhbXBhaWduMpNRAqljYW1wYWlnbjM=:state=RW ns=test:indexname=dnr-zip-idx:set=donor:bin=address:type=numeric:indextype=default:context=kiKkA3ppcA==:exp=null:state=RW ns=test:indexname=dnr-age-idx:set=donor:bin=age:type=numeric:indextype=default:context=null:exp=null:state=RW ``` Related: [sindex](#sindex)[sindex-stat](#sindex-stat) --- #### `sindex-stat` Command: ```bash sindex-stat:namespace=NAMESPACE_NAME;indexname=INDEXNAME ``` Descriptions: Display secondary index statistics, including selectivity (`entries_per_bval`). This command supplants the `sindex[/NAMESPACE[/SINDEX]]` command. These stats are HLL approximations that get refreshed hourly and become more precise. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: namespace Namespace name where the target secondary indexes reside. `ns=NAMESPACE_NAME` is deprecated since Database 7.2.0. --- indexname Name of the secondary index to query statistics from. Output: Returns a semicolon separated list of index statistics name-value pairs. `entries` is the number of records indexed. `used_bytes` storage used by this secondary index. `entries_per_bval` is the index selectivity. A lower value means the index is highly selective and queries match fewer records. Having 1 record per bin value means this is de-facto a unique index, one record per distinct value (an antipattern in Aerospike; implement a lookup table for that). `entries_per_rec` should be 1 unless a list of values is indexed. `load_pct` percentage progress toward building this secondary index. `load_time` time taken to populate this secondary index. `stat_gc_recs` is the number of records garbage collected from this secondary index Before Database 6.0.0 `ibtr_memory_used` and `nbtr_memory_used` returned memory usage information. Examples: Get statistics for a specific secondary index. ```bash asinfo -l -v 'sindex-stat:namespace=test;indexname=test_idx' # entries=10000 # used_bytes=16777216 # entries_per_bval=1429 # entries_per_rec=1 # load_pct=100 # load_time=30 # stat_gc_recs=0 ``` Related: [sindex](#sindex)[sindex-list](#sindex-list) --- #### `sindex` Command: ```bash sindex[/NAMESPACE[/SINDEX]] ``` Descriptions: Deprecated in Database 8.1.0. \* When calling sindex without either a namespace or set, use [`sindex-list`](https://aerospike.com/docs/database/reference/info#sindex-list). \* When calling sindex with a namespace but without a set, use `sindex-list`. \* When calling sindex with both namespace and set, use `sindex-stat`. Returns a list of secondary indexes defined on Aerospike and their state. To get the base64-encoded context of a secondary index, use `sindex-list`. Introduced: 3.3.0 Deprecated: 8.1.0 Removed: \- Permission: \- Parameters: NAMESPACE Name of the namespace to query for secondary indexes. --- SINDEX Name of the secondary index to query statistics from. Output: secondary index List Semicolon ’;’ delimited list of colon ’:’ delimited general statistics for secondary indexes. --- secondary index Statistics Semicolon ’;’ delimited list of detailed statistics for a particular secondary index. Examples: Query All secondary indexes ```bash asinfo -v 'sindex' ns=test:set=demo:indexname=str_idx:bin=str_bin:type=STRING:indextype=DEFAULT:path=str_bin:state=RW \ ns=test:set=demo:indexname=str_uniq_idx:bin=str_uniq_bin:type=STRING:indextype=DEFAULT:path=str_uniq_bin:state=RW \ ns=test:set=demo:indexname=int_uniq_idx:bin=int_uniq_bin:type=NUMERIC:indextype=DEFAULT:path=int_uniq_bin:state=RW ``` --- Query All secondary indexes for a Namespace ```bash asinfo -v 'sindex/test' ns=test:set=demo:indexname=str_idx:bin=str_bin:type=STRING:indextype=DEFAULT:path=str_bin:state=RW \ ns=test:set=demo:indexname=str_uniq_idx:bin=str_uniq_bin:type=STRING:indextype=DEFAULT:path=str_uniq_bin:state=RW \ ns=test:set=demo:indexname=int_uniq_idx:bin=int_uniq_bin:type=NUMERIC:indextype=DEFAULT:path=int_uniq_bin:state=RW ``` --- Query Statistics for a Particular secondary index ```bash asinfo -v 'sindex/test/str_idx' keys=9;entries=9000;ibtr_memory_used=18688;nbtr_memory_used=162009; \ load_pct=100;loadtime=6;write_success=10000;write_error=0; \ delete_success=1000;delete_error=0;stat_gc_recs=0; \ query_basic_complete=170;query_basic_error=0;query_basic_abort=0;query_basic_avg_rec_count=1000;histogram=false ``` Related: [sindex-create](#sindex-create)[sindex-delete](#sindex-delete)[sindex-list](#sindex-list)[sindex-stat](#sindex-stat)[sindex-histogram](#sindex-histogram) --- #### `smd-show` Command: ```bash smd-show:module=[module name] ``` Descriptions: Shows information about the specified [SMD module](https://aerospike.com/docs/database/manage/database/directory-structure#run-time-directories). Available modules are “evict”, “roster”, “sindex”, “truncate”, “UDF”, and “XDR”. The “security” module is not available. Introduced: 6.1.0 Deprecated: \- Removed: \- Permission: \- Output: Returns persisted information about the specified module. Examples: Execute Command ```bash asinfo -v "smd-show:module=truncate" test=392594196771;test|eg-set=394219746122 ``` --- #### `statistics` Command: ```bash statistics ``` Descriptions: Returns system health and usage stats for this server. For XDR-related metrics, use [`get-stats`](https://aerospike.com/docs/database/reference/info#get-stats). Use option -l for pretty print. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Output: A semicolon ”;” delimited list of system health and usage statistics of form “METRIC:VALUE”. The -l option breaks up statistics on individual lines. Examples: Collect system metrics for a particular node running on localhost - print each metric on a new line. ```bash asinfo -v 'statistics' -l failed_best_practices=true cluster_size=1 cluster_key=F6F7CE8A5621 cluster_generation=1 cluster_principal=BB937664A290C00 cluster_min_compatibility_id=10 cluster_max_compatibility_id=10 cluster_integrity=true cluster_is_member=true cluster_duplicate_nodes=null cluster_clock_skew_stop_writes_sec=0 cluster_clock_skew_ms=0 cluster_clock_skew_outliers=null uptime=2167 system_total_cpu_pct=8 system_user_cpu_pct=5 system_kernel_cpu_pct=3 system_free_mem_kbytes=5930052 system_free_mem_pct=48 system_thp_mem_kbytes=0 process_cpu_pct=1 threads_joinable=8 threads_detached=65 threads_pool_total=46 threads_pool_active=46 heap_allocated_kbytes=127219 heap_active_kbytes=129288 heap_mapped_kbytes=251904 heap_efficiency_pct=51 heap_site_count=0 objects=9009 tombstones=0 info_queue=0 rw_in_progress=0 proxy_in_progress=0 tree_gc_queue=0 client_connections=2 client_connections_opened=14398 client_connections_closed=14396 heartbeat_connections=0 heartbeat_connections_opened=0 heartbeat_connections_closed=0 fabric_connections=0 fabric_connections_opened=0 fabric_connections_closed=0 heartbeat_received_self=14375 heartbeat_received_foreign=0 reaped_fds=0 info_complete=3228 demarshal_error=0 early_tsvc_client_error=73 early_tsvc_from_proxy_error=0 early_tsvc_batch_sub_error=0 early_tsvc_from_proxy_batch_sub_error=0 early_tsvc_udf_sub_error=0 early_tsvc_ops_sub_error=0 batch_index_initiate=0 batch_index_queue=0:0,0:0,0:0,0:0 batch_index_complete=0 batch_index_error=0 batch_index_timeout=0 batch_index_delay=0 batch_index_unused_buffers=0 batch_index_huge_buffers=0 batch_index_created_buffers=0 batch_index_destroyed_buffers=0 batch_index_proto_uncompressed_pct=0.000 batch_index_proto_compression_ratio=1.000 scans_active=0 query_short_running=0 query_long_running=0 paxos_principal=BB937664A290C00 time_since_rebalance=2165 migrate_allowed=true migrate_partitions_remaining=0 fabric_bulk_send_rate=0 fabric_bulk_recv_rate=0 fabric_ctrl_send_rate=0 fabric_ctrl_recv_rate=0 fabric_meta_send_rate=0 fabric_meta_recv_rate=0 fabric_rw_send_rate=0 fabric_rw_recv_rate=0 ``` Related: [bins](#bins)[namespace](#namespace)[sets](#sets)[get-stats](#get-stats) --- #### `status` Command: ```bash status ``` Descriptions: Always returns ok. Verifies service port is open. Useful when using telnet. In asinfo, leave off the value ‘-v’ argument. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Output: If server is up, always returns ‘ok’ --- #### `thread-traces` Command: ```bash thread-traces ``` Descriptions: Returns the current call stack for all server threads. Introduced: 4.5.3 Deprecated: \- Removed: \- Permission: \- Output: For each server thread, returns its ID (the first number on the dashed line), the offset of its run function (in parentheses on the dashed line), and its current call stack. Because there are typically over 100 server threads, this command can generate a large amount of output. Examples: Sample output (for one thread only) ```bash asinfo -v 'thread-traces' -l ---------- 45387 (0x12914f) ---------- /usr/bin/asd(cf_thread_traces_action+0x4c) [0x67807c] /lib64/libpthread.so.0() [0x384720f710] /lib64/libc.so.6(nanosleep+0x2d) [0x3846eaca3d] /lib64/libc.so.6(usleep+0x34) [0x3846ee1be4] /usr/bin/asd(hb_adjacency_tender+0x275) [0x5293c4] /usr/bin/asd() [0x678379] /lib64/libpthread.so.0() [0x38472079d1] /lib64/libc.so.6(clone+0x6d) [0x3846ee88fd] ``` --- #### `throughput` Command: ```bash throughput:[hist=HISTOGRAM;][back=BACK;][duration=DURATION;][slice=SLICE] ``` Descriptions: Returns throughput info. Introduced: 3.9.0 Deprecated: \- Removed: 5.1.0 Permission: \- Parameters: hist Histogram name - if none is provided, command applies to all namespace tracked histograms, which are the read, write, UDF and query histograms’. \[Default: all namespace tracked histograms\] Options (`ns` being the namespace name): - {ns}-read - {ns}-write - {ns}-udf - {ns}-query - batch-index To know more about histograms, see [Monitoring latencies](https://aerospike.com/docs/database/observe/latency). --- back Start search this many seconds before now. \[Default: Minimum to get last slice.\] Note: `back=0` queries starting from oldest cache. --- duration seconds (forward) from start to search. \[Default: 0, everything to present\] --- slice Intervals (in seconds) to analyze. \[Default: 0, everything as one slice\] Output: Return value is in the following format: `HISTOGRAM_0:TIME_START,ops/sec,THRESHHOLD_0,THRESHHOLD_1,...;HISTOGRAM_1:...` Examples: Show All throughput Histograms ```bash asinfo -v 'throughput:' {ns}-read:23:56:38-GMT,ops/sec;23:56:48,0.0;{ns}-write:23:56:38-GMT,ops/sec;23:56:48,0.0; error-no-data-yet-or-back-too-small;error-no-data-yet-or-back-too-small ``` --- Show Read throughput Histogram ```bash asinfo -v 'throughput:hist={ns}-read;slice=30;back=300;duration:120' {ns}-read:23:51:28-GMT,ops/sec;23:51:58,0.0;23:52:28,0.0;23:52:58,0.0; 23:53:28,0.0;23:53:58,0.0;23:54:28,0.0;23:54:58,0.0;23:55:28,0.0;23:55:58,0.0 ``` Related: [hist-track-start](#hist-track-start)[hist-track-stop](#hist-track-stop)[latency](#latency) --- #### `tip-clear` Command: ```bash tip-clear:host-port-list=Node1:3002,Node2:3002,... ``` Descriptions: Clear configured hostname(s) from seed list for mesh-mode heartbeats. Configured hostname(s) means the hostname(s) from config file or added using the [`tip`](https://aerospike.com/docs/database/reference/info#tip) command. Useful in the case of repurposing a node from a live cluster. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: sys-admin Parameters: host-port-list Configured hostname(s) and port(s) of Aerospike seeds that need to be removed from the seed list. Clears the dynamic list of hostnames loaded from [`mesh-seed-address-port`](https://aerospike.com/docs/database/reference/config#network__mesh-seed-address-port) or using the tip command. - Starting with Database 5.3.0, supports only configured hostname(s). - Starting with Database 5.3.0, does not support the value ‘all’. - Starting with Database 3.9.0.X to 5.2.X, it also honors IP addresses of active nodes (seed or non-seed). - Starting with Database 3.10.0, when specifying ‘all’, both seed nodes and discovered nodes are cleared. - Starting with Database 3.9.1, the parameter host-port-list is always required (even for specifying ‘all’). Output: Generates descriptive messages on success as well as a failure. Examples: Clear configured hostname(s) from seed list ```bash asinfo -v 'tip-clear:host-port-list=172.17.0.15:3002' asinfo -v 'tip-clear:host-port-list=prod_aerospike_2:3002' ``` Related: [mesh](#mesh)[tip](#tip) --- #### `tip` Command: ```bash tip:host=HOST;port=MESH-PORT ``` Descriptions: Add hostname to seed list for mesh-mode heartbeats. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: sys-admin Parameters: host Hostname of an Aerospike server to join this cluster. --- port Mesh port of an Aerospike server to join this cluster. Output: Command generates descriptive messages on success as well as a failure. Examples: Adding a Host to the Cluster ```bash asinfo -v 'tip:host=172.16.121.138;port=3002' asinfo -h prod_aerospike_1 -v "tip:host=prod_aerospike_2;port=3002" ``` Related: [mesh](#mesh)[tip-clear](#tip-clear) --- #### `truncate-namespace-undo` Command: ```bash truncate-namespace-undo:namespace=NAMESPACE_NAME; ``` Descriptions: Undo a [`truncate-namespace`](https://aerospike.com/docs/database/reference/info#truncate-namespace)command by removing the associated System Meta Data (SMD) files entry and allow (some) previously truncated records to be resurrected on the subsequent cold restart (only for records that have not had their persisted storage block overwritten by other records). Run this command from asadm instead of asinfo. You need either the write permission (Database 5.1.0 - 5.7) or the truncate permission (Database 6.0.0+) or the data-admin permission: - For write or truncate privileges limited to running truncate-related commands only for namespaces (scoped for namespaces), the truncation to be undone requires that the namespace exist on the node where the command is issued. If the write privilege is global (not limited to namespaces), the command can be issued on any node in the cluster. - For the data-admin privilege, the truncation to be undone does _not_ require that the namespace exist on the node where the command is issued. - The equivalent command in asadm is [`manage truncate undo ns NAMESPACE_NAME {set SET_NAME}`](https://aerospike.com/docs/database/tools/asadm/live-mode/#truncate). Introduced: 4.3.1.11, 4.4.0.11, 4.5.0.6, 4.5.1.5 Deprecated: \- Removed: \- Permission: truncate Parameters: namespace Required - Name of the namespace to run the undo truncate-namespace command against. Will remove namespace level truncate entry in SMD (which persists - tombstone like - the truncate time). Output: ok Examples: Remove truncate entry in SMD for a namespace ```bash asinfo -v 'truncate-namespace-undo:namespace=test;' ``` Related: [truncate-namespace](#truncate-namespace)[truncate](#truncate)[truncate-undo](#truncate-undo) --- #### `truncate-namespace` Command: ```bash truncate-namespace:namespace=NAMESPACE_NAME;lut=TIME ``` Descriptions: Deletes every record in the specified namespace where the last update time (LUT) is older than the given time. Run this command from `asadm` instead of `asinfo`. Do not mix the ‘truncate’ command with [transactions](https://aerospike.com/docs/database/manage/namespace/sets#pause-and-drain-transactions-before-truncating). - Parameters: `namespace` is required, `lut` is optional. - This operation skips the special transaction set iso-8601|unix-epoch}`](https://aerospike.com/docs/database/tools/asadm/live-mode/#truncate). Introduced: 4.3.1.11, 4.4.0.11, 4.5.0.6, 4.5.1.5 Deprecated: \- Removed: \- Permission: truncate Parameters: namespace Required - Name of the namespace to truncate. --- lut Optional - Last update time (LUT). If not specified, the current time is used. The LUT is expressed as Unix epoch (UTC) nanoseconds, unlike record metadata LUT and [truncate\_lut](https://aerospike.com/docs/database/reference/metrics#namespace__truncate_lut), which are in Citrusleaf epoch (00:00:00 UTC on 1 Jan 2010) format. It can be given in hex (with a 0x prefix), decimal, or octal (with a 0 prefix). The LUT is not allowed to be older than the Citrusleaf epoch, and is not allowed to be beyond the current time (that is, in the future). “lut=now” to mean the current time, is no longer supported as of version 4.3.1.11 (and later 4.3.1.X), 4.4.0.11 (and later 4.4.0.X), 4.5.0.6 (and later 4.5.0.X) and 4.5.1.5 later. Output: ok Examples: Truncate a namespace ```bash asinfo -v 'truncate-namespace:namespace=test;' ``` Related: [truncate-namespace-undo](#truncate-namespace-undo)[truncate](#truncate)[truncate-undo](#truncate-undo) --- #### `truncate-undo` Command: ```bash truncate-undo:namespace=NAMESPACE_NAME;set=SET_NAME; ``` Descriptions: Undo a [`truncate`](https://aerospike.com/docs/database/reference/info?search=truncate-namespace#truncate) command by removing the associated SMD (System Meta Data) files entry and allow (some) previously truncated records to be resurrected on the subsequent cold restart (only for records that have not had their persisted storage block overwritten by other records). Run this command from asadm instead of asinfo. You need either the write permission or the data-admin permission: - For write privilege limited to running truncate-related commands only for namespaces (scoped for namespaces), the truncation to be undone requires that the namespace exist on the node where the command is issued. If the write privilege is global (not limited to namespaces), the command can be issued on any node in the cluster. - For the data-admin privilege, the truncation to be undone does _not_ require that the namespace exist on the node where the command is issued. The equivalent command in asadm is [`manage truncate undo NAMESPACE_NAME {set SET_NAME}`](https://aerospike.com/docs/database/tools/asadm/live-mode/#truncate). Introduced: 3.12.0 Deprecated: \- Removed: \- Permission: truncate Parameters: namespace Required - Name of the namespace to run the undo truncate command against. Will only remove namespace level truncate entry in SMD (which persists - tombstone like - the truncate time) if set is not specified. --- set Name of the set to run the undo truncate command against. The `set` parameter is required. Output: ok Examples: Remove truncate entry in SMD for a namespace or a set ```bash asinfo -v 'truncate-undo:namespace=test;' asinfo -v 'truncate-undo:namespace=test;set=set1;' ``` Related: [truncate](#truncate)[truncate-namespace](#truncate-namespace)[truncate-namespace-undo](#truncate-namespace-undo) --- #### `truncate` Command: ```bash truncate:namespace=NAMESPACE_NAME;set=SET_NAME;lut=TIME ``` Descriptions: The `truncate` command deletes every record in the specified set where the last update time (LUT) is older than the given time. Run this command from `asadm` instead of `asinfo`. Do not mix the ‘truncate’ command with [transactions](https://aerospike.com/docs/database/manage/namespace/sets#pause-and-drain-transactions-before-truncating). - Parameters: `namespace` and `set` are required; `lut` is optional. - Deletes are durable and preserve record deletions in the Enterprise Edition only. - Role-based access control [privileges](https://aerospike.com/docs/database/manage/security/rbac#privileges) are required: - `write` privileges are required for Database 5.1.0 - 5.7. - `truncate` privileges are required for Database 6.1.0 and later. - Command is issued on one node in a cluster and then is distributed to other nodes using system metadata (SMD); see [During cluster change](https://aerospike.com/docs/database/manage/namespace/sets#during-cluster-change). - The presence of secondary indexes can slow down truncation. See [Manage sindexes](https://aerospike.com/docs/database/manage/namespace/sets#manage-sindexes). - To truncate an entire namespace, use [truncate-namespace](https://aerospike.com/docs/database/reference/info#truncate-namespace). - A successful response from the node the command is issued against, the targeted set would appear as entirely deleted from any application’s perspective, regardless of how long it would take to actually delete all the records assuming all the nodes are in the cluster. - The equivalent command in `asadm` is \[`manage truncate ns NAMESPACE {set SET} {before iso-8601|unix-epoch}](/database/tools/asadm/live-mode/#truncate)`. Introduced: 3.12.0 Deprecated: \- Removed: \- Permission: truncate Parameters: namespace Required - Name of the namespace with the set to be truncated. --- set Required - Truncates only the set. Set name cannot be _null_. To truncate an entire namespace, use [truncate-namespace](https://aerospike.com/docs/database/reference/info#truncate-namespace). --- lut Optional - Last update time (LUT). If not specified, the current time is used. The LUT is expressed as Unix epoch (UTC) nanoseconds, unlike record metadata LUT and [truncate\_lut](https://aerospike.com/docs/database/reference/metrics#namespace__truncate_lut), which are in Citrusleaf epoch (00:00:00 UTC on 1 Jan 2010) format. It can be given in hex with a 0x prefix, decimal, or octal with a 0 prefix. The LUT cannot be older than the Citrusleaf epoch, and cannot be beyond the current time. “lut=now” to mean the current time, is not supported. Output: ok Examples: Truncate commands 1. Truncate records in set1 in namespace 'test' with a LUT before the current time. 2. Truncate records in set1 in namespace 'test' with a LUT before 2018-04-01 09:00:00 UTC. ```bash 1. asinfo -v 'truncate:namespace=test;set=set1;' 2. asinfo -v 'truncate:namespace=test;set=set1;lut=1522573200000000000;' ``` Related: [truncate-undo](#truncate-undo)[truncate-namespace](#truncate-namespace)[truncate-namespace-undo](#truncate-namespace-undo) --- #### `udf-get` Command: ```bash udf-get ``` Descriptions: Get the content of a registered UDF from the node. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Parameters: filename The filename of the registered UDF to get. Output: The type and Base64-encoded content of a registered UDF on the local node. Examples: ```bash asinfo -v "udf-get:filename=basic_udf.lua" type=LUA;content=LS0gQSB2ZXJ5IHNpbXBsZSBhcml0aG1ldGljIFVERiB3aXRoIG5vIGFyZ3VtZW50cyBvciByZXR1cm4gdmFsdWUuCi0tIEl0IGFkZHMgMTAwMCB0byB0aGUgdmFsdWUgaW4gYmluICd0ZXN0LWJpbi0xJyBhbmQgdXBkYXRlcyBpdC4KZnVuY3Rpb24gdGVzdF9iaW5fMV9hZGRfMTAwMChyZWMpCglyZWNbJ3Rlc3QtYmluLTEnXSA9IHJlY1sndGVzdC1iaW4tMSddICsgMTAwMAoJYWVyb3NwaWtlOnVwZGF0ZShyZWMpCmVuZAoKLS0gQSBzaW1wbGUgYXJpdGhtZXRpYyBVREYgdGhhdCBoYXMgYXJndW1lbnRzIGFuZCBhIHJldHVybiB2YWx1ZS4KLS0gSXQgdXBkYXRlcyB0aGUgdmFsdWUgaW4gdGhlIHNwZWNpZmllZCBiaW4gYWZ0ZXIgcGVyZm9ybWluZyB0aGUgYXJpdGhtZXRpYwotLSBvcGVyYXRpb24sIGFuZCByZXR1cm5zIHRoZSByZXN1bHRpbmcgYmluIHZhbHVlLgpmdW5jdGlvbiBiaW5fdHJhbnNmb3JtKHJlYywgYmluX25hbWUsIHgsIHkpCglyZWNbYmluX25hbWVdID0gKHJlY1tiaW5fbmFtZV0gKiB4KSArIHkKCWFlcm9zcGlrZTp1cGRhdGUocmVjKQoJcmV0dXJuIHJlY1tiaW5fbmFtZV0KZW5kCgo= ``` Related: [udf-list](#udf-list)[udf-put](#udf-put)[udf-remove](#udf-remove) --- #### `udf-list` Command: ```bash udf-list ``` Descriptions: Lists the registered UDF/Lua modules on the node. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: \- Output: A list of registered UDF modules. Examples: ```bash asinfo -v "udf-list" filename=basic_udf.lua,hash=706c57cb29e027221560a3cb4b693573ada98bf2,type=LUA ``` Related: [udf-put](#udf-put)[udf-get](#udf-get)[udf-remove](#udf-remove) --- #### `udf-put` Command: ```bash udf-put ``` Descriptions: Registers a UDF/Lua module on the node. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: udf-admin Parameters: filename The filename to register the UDF as. --- udf-type Currently can only be the string “lua”. --- content-len Number of bytes to expect for the base64 encoded UDF content. --- content The Base64-encoded content of the UDF. Examples: ```bash asinfo -v "udf-put:filename=basic_udf.lua;udf-type=LUA;content-len=760;content=LS0gQSB2ZXJ5IHNpbXBsZSBhcml0aG1ldGljIFVERiB3aXRoIG5vIGFyZ3VtZW50cyBvciByZXR1cm4gdmFsdWUuCi0tIEl0IGFkZHMgMTAwMCB0byB0aGUgdmFsdWUgaW4gYmluICd0ZXN0LWJpbi0xJyBhbmQgdXBkYXRlcyBpdC4KZnVuY3Rpb24gdGVzdF9iaW5fMV9hZGRfMTAwMChyZWMpCglyZWNbJ3Rlc3QtYmluLTEnXSA9IHJlY1sndGVzdC1iaW4tMSddICsgMTAwMAoJYWVyb3NwaWtlOnVwZGF0ZShyZWMpCmVuZAoKLS0gQSBzaW1wbGUgYXJpdGhtZXRpYyBVREYgdGhhdCBoYXMgYXJndW1lbnRzIGFuZCBhIHJldHVybiB2YWx1ZS4KLS0gSXQgdXBkYXRlcyB0aGUgdmFsdWUgaW4gdGhlIHNwZWNpZmllZCBiaW4gYWZ0ZXIgcGVyZm9ybWluZyB0aGUgYXJpdGhtZXRpYwotLSBvcGVyYXRpb24sIGFuZCByZXR1cm5zIHRoZSByZXN1bHRpbmcgYmluIHZhbHVlLgpmdW5jdGlvbiBiaW5fdHJhbnNmb3JtKHJlYywgYmluX25hbWUsIHgsIHkpCglyZWNbYmluX25hbWVdID0gKHJlY1tiaW5fbmFtZV0gKiB4KSArIHkKCWFlcm9zcGlrZTp1cGRhdGUocmVjKQoJcmV0dXJuIHJlY1tiaW5fbmFtZV0KZW5kCgo=;" ok ``` --- ```bash asinfo -v "udf-put:filename=basic_udf.lua;udf-type=LUA;content-len=760;content=LS0gQSB2ZXJ5IHNpbXBsZSBhcml0aG1ldGljIFVERiB3aXRoIG5vIGFyZ3VtZW50cyBvciByZXR1cm4gdmFsdWUuCi0tIEl0IGFkZHMgMTAwMCB0byB0aGUgdmFsdWUgaW4gYmluICd0ZXN0LWJpbi0xJyBhbmQgdXBkYXRlcyBpdC4KZnVuY3Rpb24gdGVzdF9iaW5fMV9hZGRfMTAwMChyZWMpCglyZWNbJ3Rlc3QtYmluLTEnXSA9IHJlY1sndGVzdC1iaW4tMSddICsgMTAwMAoJYWVyb3NwaWtlOnVwZGF0ZShyZWMpCmVuZAoKLS0gQSBzaW1wbGUgYXJpdGhtZXRpYyBVREYgdGhhdCBoYXMgYXJndW1lbnRzIGFuZCBhIHJldHVybiB2YWx1ZS4KLS0gSXQgdXBkYXRlcyB0aGUgdmFsdWUgaW4gdGhlIHNwZWNpZmllZCBiaW4gYWZ0ZXIgcGVyZm9ybWluZyB0aGUgYXJpdGhtZXRpYwotLSBvcGVyYXRpb24sIGFuZCByZXR1cm5zIHRoZSByZXN1bHRpbmcgYmluIHZhbHVlLgpmdW5jdGlvbiBiaW5fdHJhbnNmb3JtKHJlYywgYmluX25hbWUsIHgsIHkpCglyZWNbYmluX25hbWVdID0gKHJlY1tiaW5fbmFtZV0gKiB4KSArIHkKCWFlcm9zcGlrZTp1cGRhdGUocmVjKQoJcmV0dXJuIHJlY1tiaW5fbmFtZV0KZW5=;" error=invalid_content ``` Related: [udf-list](#udf-list)[udf-get](#udf-get)[udf-remove](#udf-remove) --- #### `udf-remove` Command: ```bash udf-remove ``` Descriptions: Removes a previously registered UDF module. Introduced: 3.3.0 Deprecated: \- Removed: \- Permission: udf-admin Parameters: filename The filename of the UDF to remove. Examples: ```bash asinfo -v "udf-remove:filename=basic_udf.lua" ok ``` Related: [udf-list](#udf-list)[udf-get](#udf-get)[udf-put](#udf-put) --- #### `user-agents` Command: ```bash asinfo -v "user-agents" ``` Descriptions: Enables tracking of client versions to help administrators maintain version compatibility and operational stability. Returns a list of all user agents found on an active socket, with a count of how many times seen. From the perspective of the server, the user agent is an opaque set of 64 bytes provided by the client. Introduced: 8.1.0 Deprecated: \- Removed: \- Permission: \- Output: Examples: Raw command output ```bash asinfo -v "user-agents" user-agent=MSxhc2FkbS00LjAuMCx1bmtub3du:count=1 ``` --- asadm "show user-agents" sample output ```bash Admin> show user-agents ~User Agent Information (2025-08-01 22:40:26 UTC)~ Node| Client| App ID|Count | Version| | 127.0.0.1:3100|asadm-4.0.0|unknown| 2 Number of rows: 1 ``` --- Sample output user agent list filtered by specific node ```bash Admin> show user-agents with 10.1.* ~User Agent Information (2025-08-01 22:40:51 UTC)~ Node| Client| App ID|Count | Version| | 10.1.1.1:3100 |asadm-4.0.0|unknown| 1 10.1.1.1:3000 |java-9.1.0 |buymeit| 2 10.1.1.1:3000 |unknown |unknown| 27 Number of rows: 3 ``` --- #### `version` Command: ```bash version ``` Descriptions: Returns the full server version string including edition and build number. Deprecated in Database 8.1.1.0. Use [`release`](https://aerospike.com/docs/database/reference/info#release) instead. Introduced: 3.3.0 Deprecated: 8.1.1.0 Removed: \- Permission: \- Output: Full version string, such as _Aerospike Enterprise Edition build 8.1.0.0_ Examples: Execute Command ```bash asinfo -v 'version' Aerospike Enterprise Edition build 8.1.0.0 ``` Related: [release](#release) --- #### `xdr-command` Command: ```bash xdr-command: ``` Descriptions: Issues commands for XDR in server 3.8 and later. Introduced: 3.8.3 Deprecated: \- Removed: 5.0.0 Permission: sys-admin Parameters: skip-outstanding This command instructs XDR to skip all outstanding records in the digest log. It only skips outstanding records for the main thread (does not impact potential link down and failed node threads). --- handle-failednode=true|false When set to false, it instructs XDR to skip all outstanding records for the failed node thread for the current and potential upcoming occurrences of failed node processing. This command should only be used for rolling restart situations where all the nodes are expected to join the cluster back (if handle-failednode is set to false and a node is permanently removed from the cluster, digestlog space would not be reclaimed). Consult Aerospike Support prior to using this command. --- handle-linkdown=true|false When set to false, it instructs XDR to skip all outstanding records for the linked down thread for the current and potential upcoming occurrences of linked down processing. We recommend that you consult with Aerospike Support prior to using this command. --- force-linkdown=true|false;dc=DC\_NAME Available starting with Database 4.1.0. When set to true, forces a DC into CLUSTER\_DOWN state regardless if the DC is reachable or not. Should be set back to false to get the cluster into CLUSTER\_WINDOW\_SHIP. The use of this command should be carefully considered. Putting a cluster in CLUSTER\_DOWN state for an extended period of time causes the digest log to potentially overflow (and hit stop writes if configured as such) and forces an extra thread to handle shipping for the window the cluster was in the CLUSTER\_DOWN state. Examples: Skip outstanding record in the digest log ```bash asinfo -v 'xdr-command:skip-outstanding' ok asinfo -v 'xdr-command:handle-failednode=false' ok asinfo -v 'xdr-command:force-linkdown=true;dc=DC1' ok ``` --- #### `xdr-get-filter` Command: ```bash xdr-get-filter:dc=DCNAME;namespace=NAMESPACE_NAME[;b64=TRUE|FALSE] ``` Descriptions: Checks which filter is set in XDR. Introduced: 5.3.0 Deprecated: \- Removed: \- Permission: \- Output: Shows the existing filter for a namespace in the DC. Expression appears as ‘null’ if there is no filter. (Starting with Database 7.2.0, use “NAMESPACE\_NAME” instead of ns=NAME”.\`) Examples: Get filter for 'test' namespace in 'DC1' ```bash asinfo -v "xdr-get-filter:dc=DC1;namespace=test" ``` --- Get filter for 'test' namespace in 'DC1' in base-64 format ```bash asinfo -v "xdr-get-filter:dc=DC1;namespace=test;b64=true" ``` --- #### `xdr-set-filter` Command: ```bash xdr-set-filter:dc=DC_NAME;namespace=NAMESPACE_NAME;exp= ``` Descriptions: Specifies which records are shipped by XDR using base64 equivalent of the expressions syntax. Use ‘exp=null’ to remove an existing filter. Introduced: 5.3.0 Deprecated: \- Removed: \- Permission: sys-admin Output: Upon success command returns “ok” Examples: Set filter for 'test' namespace in 'DC1' ```bash asinfo -v "xdr-set-filter:dc=DC1;namespace=test;exp=kxGRSJMEk1ECo2FnZRU=" ``` --- Remove filter for 'test' namespace in 'DC1' ```bash asinfo -v "xdr-set-filter:dc=DC1;namespace=test;exp=null" ``` ---