DEPOT_EVICTIONS

Records data on eviction of objects from the depot.

Eon Mode only

Records data on eviction of objects from the depot.

Column Name Data Type Description
START_TIME TIMESTAMP Demarcate the start and end of each depot eviction operation.
END_TIME
NODE_NAME VARCHAR Name of a node where the eviction occurred.
SESSION_ID VARCHAR Unique numeric ID assigned by the Vertica catalog, which identifies the session for which profiling information is captured. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
USER_ID INTEGER Unique numeric ID assigned by the Vertica catalog, which identifies the user.
USER_NAME VARCHAR The user who made changes to the depot.
TRANSACTION_ID INTEGER Identifier for the transaction within the session, if any. If a session is active but no transaction has begun, TRANSACTION_ID returns NULL.
STATEMENT_ID INTEGER Unique numeric ID for the statement that caused the eviction. NULL indicates that no statement is currently being processed. The combination of TRANSACTION_ID and STATEMENT_ID uniquely identifies a statement within a session; these columns are useful for creating joins with other system tables.
REQUEST_ID INTEGER Unique identifier of the query request in the user session.
STORAGE_ID VARCHAR Unique hexadecimal numeric ID assigned by the Vertica catalog, which identifies the storage.
STORAGE_OID INTEGER Numeric ID assigned by the Vertica catalog, which identifies the storage.
FILE_SIZE_BYTES INTEGER The size of the file in bytes that was evicted.
NUMBER_HITS INTEGER The number of times the file was accessed.
LAST_ACCESS_TIME TIMESTAMP The last time the file was read.
REASON VARCHAR

The reason the file was evicted, one of the following:

  • CLEAR DEPOT

  • DEPOT FILL AT STARTUP

  • DEPOT SIZE CHANGE

  • DROP OBJECT

  • DROP SUBSCRIPTION

  • EVICTION DUE TO NEW

  • LOAD

  • PEER TO PEER FILL

  • QUERY

IS_PINNED BOOLEAN Whether the object has a pinning policy.
IS_ANTI_PINNED BOOLEAN Whether the object has an anti-pinning policy.

Examples

=> SELECT * FROM V_MONITOR.DEPOT_EVICTIONS LIMIT 2;
-[ RECORD 1 ]----+-------------------------------------------------
start_time       | 2019-02-20 15:32:26.765937+00
end_time         | 2019-02-20 15:32:26.766019+00
node_name        | v_verticadb_node0001
session_id       | v_verticadb_node0001-8997:0x3e
user_id          | 45035996273704962
user_name        | dbadmin
transaction_id   | 45035996273705450
statement_id     | 1
request_id       | 406
storage_id       | 0000000000000000000000000000000000a000000001fbf6
storage_oid      | 45035996273842065
file_size_bytes  | 61
number_hits      | 1
last_access_time | 2019-02-20 15:32:26.668094+00
reason           | DROP OBJECT
is_pinned        | f
-[ RECORD 2 ]----+-------------------------------------------------
start_time       | 2019-02-20 15:32:26.812803+00
end_time         | 2019-02-20 15:32:26.812866+00
node_name        | v_verticadb_node0001
session_id       | v_verticadb_node0001-8997:0x3e
user_id          | 45035996273704962
user_name        | dbadmin
transaction_id   | 45035996273705453
statement_id     | 1
request_id       | 409
storage_id       | 0000000000000000000000000000000000a000000001fbf6
storage_oid      | 45035996273842079
file_size_bytes  | 91
number_hits      | 1
last_access_time | 2019-02-20 15:32:26.770807+00
reason           | DROP OBJECT
is_pinned        | f