The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-21. For the latest, interactive version please visit https://mariadb.com/kb/.

Spider Status Variables

Contents

  1. Spider_direct_aggregate
  2. Spider_direct_delete
  3. Spider_direct_order_limit
  4. Spider_direct_update
  5. Spider_mon_table_cache_version
  6. Spider_mon_table_cache_version_req
  7. Spider_parallel_search

The following status variables are associated with the Spider storage engine. See Server Status Variables for a complete list of status variables that can be viewed with SHOW STATUS.

See also the Full list of MariaDB options, system and status variables.

Spider_direct_aggregate

  • Description: Number of times direct aggregate has happened in spider. That is, in a partitioned spider table, instead of scanning individual rows in remote tables corresponding to partitions for aggregation functions like SUM and COUNT, spider forwards aggregate queries to these tables directly and aggregate the results.
  • Scope: Global, Session
  • Data Type: numeric

Spider_direct_delete

  • Description:
  • Scope: Global, Session
  • Data Type: numeric
  • Introduced: MariaDB 10.3.3

Spider_direct_order_limit

  • Description:
  • Scope: Global, Session
  • Data Type: numeric

Spider_direct_update

  • Description:
  • Scope: Global, Session
  • Data Type: numeric
  • Introduced: MariaDB 10.3.3

Spider_mon_table_cache_version

  • Description: The version of the spider monitoring table cache, always less than or equal to Spider_mon_table_cache_version_req. If the inequality is strict, then the cache is refreshed when the spider udf spider_ping_table is called. When the cache is refreshed, the value of Spider_mon_table_cache_version is brought up to be the same value as Spider_mon_table_cache_version_req.
  • Scope: Global, Session
  • Initial value: 0
  • Data Type: numeric

Spider_mon_table_cache_version_req

  • Description: The required version of the spider monitoring table cache. A call to the spider udf spider_flush_table_mon_cache will cause its value to be incremented by one, thus ensuring a refresh of the cache will happen when needed.
  • Scope: Global, Session
  • Initial value: 1
  • Data Type: numeric
  • Description:
  • Scope: Global, Session
  • Data Type: numeric
  • Introduced: MariaDB 10.3.3
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.