UDX_FENCED_PROCESSES

Provides information about processes Vertica uses to run user-defined extensions in fenced mode.

Provides information about processes Vertica uses to run user-defined extensions in fenced mode.

Column Name Data Type Description
NODE_NAME VARCHAR Name of the node that is reporting the requested information.
PROCESS_TYPE VARCHAR

Indicates what kind of side process this row is for and can be one of the following values:

  • UDxZygoteProcess — Master process that creates worker side processes, as needed, for queries. There will be, at most, 1 UP UDxZygoteProcess for each Vertica instance.

  • UDxSideProcess — Indicates that the process is a worker side process. There could be many UDxSideProcesses, depending on how many sessions there are, how many queries, and so on.

SESSION_ID VARCHAR Identifier for this session. This identifier is unique within the cluster at any point in time but can be reused when the session closes.
LANGUAGE VARCHAR The language of the UDx. For example 'R' or 'C++';
MAX_MEMORY_JAVA_KB INTEGER The maximum amount of memory in KB that can be used for the Java heap file on the node.
PID INTEGER Linux process identifier of the side process (UDxSideProcess).
PORT VARCHAR For Vertica internal use. The TCP port that the side process is listening on.
STATUS VARCHAR

Set to UP or DOWN, depending on whether the process is alive or not.

After a process fails, Vertica restarts it only on demand. So after a process failure, there might be periods of time when no side processes run.

Privileges

None