Skip to main content
When adding an Event Alert, there are many event codes to choose from. You can search through the available events in the event alert creation window using one of the event codes below or using keywords from a description of the desired event, e.g., shutdown, standby, etc. The events are organized by Kinetica component.

Cluster Operations

Event CodeSeverityDescription
01.120501.20INFOCluster system mode set to standby

Error Message

The system mode has been set to: <standby>, current status: <status>
01.120502.20INFOCluster system mode set to run

Error Message

The system mode has been set to: <run>, current status: <status>
01.120503.20INFOCluster system mode set to shutdown

Error Message

The system mode has been set to: <shutdown>, current status: <status>
01.180501.20INFOCluster system status is stopped

Error Message

The system status has changed to: <stopped>, current mode: <mode>
01.180502.20INFOCluster system status is starting

Error Message

The system status has changed to: <starting>, current mode: <mode>
01.180503.20INFOCluster system status is running

Error Message

The system status has changed to: <running>, current mode: <mode>
01.180504.40ERRORCluster system status is limited and not able to process requests

Error Message

The system status is limited and cannot process requests, please see database logs for further details.
01.180505.20INFOCluster system status is shutdown

Error Message

The system status has changed to: <shutdown>, current mode: <mode>

Data Source Subscriptions

Event CodeSeverityDescription
14.240400.20INFODatasource subscription canceled

Error Message

Canceled datasource <name> subscription
14.240800.40ERRORKafka datasource error

Error Message

<error message>
14.241500.20INFOKafka datasource info

Error Message

Kafka Statistics: ‘<info>‘
14.241500.30WARNDatasouce subscription lagging behind

Error Message

Datasource : <datasource> has increasing lag: <total_lag>
14.242700.20INFODatasource subscription started

Error Message

Started datasource <name> subscription
14.242800.20INFOKafka datasource subscription starting

Error Message

Kafka subscription validation completed for table: <table_name>
14.243000.20INFODatasource subscription terminated

Error Message

Terminated datasource <name> subscription
14.243600.20INFODatasource subscription paused

Error Message

Paused datasource <name> subscription
14.243700.20INFODatasource subscription resumed

Error Message

Resumed datasource <name> subscription
14.243800.40ERRORDatasource subscription schema error

Error Message

Schema error on <name> subscription
14.243900.20INFODatasource subscription schema change

Error Message

Schema change on <name> subscription
14.244000.30WARNDatasource subscription records skipped

Error Message

Records skipped on <name> subscription

HTTPD

Event CodeSeverityDescription
06.180503.20INFOHttpd server status changed to starting

Error Message

The httpd server status has changed on hostname:<hostname>, host_mode:<host_mode>, httpd_status:<starting>
06.180504.20INFOHttpd server status changed to running

Error Message

The httpd server status has changed on hostname:<hostname>, host_mode:<host_mode>, httpd_status:<running>
06.180505.20INFOHttpd server status changed to stopping

Error Message

The httpd server status has changed on hostname:<hostname>, host_mode:<host_mode>, httpd_status:<stopping>
06.180506.20INFOHttpd server status changed to stopped

Error Message

The httpd server status has changed on hostname:<hostname>, host_mode:<host_mode>, httpd_status:<stopped>
06.180507.40ERRORHttpd server has terminated

Error Message

The httpd server status has changed on hostname:<hostname>, host_mode:<host_mode>, httpd_status:<terminated>

High Availability (HA)

Event CodeSeverityDescription
05.080300.50FATALHA configuration error

Error Message

AMQP client hostname cannot be empty.
05.081200.50FATALHA unable to read config file

Error Message

Unable to read HA config file: <ha_conf_file>
05.081600.40ERRORHA initialization failed

Error Message

Failed to initialize the HA client - cannot create queues.
05.081600.50FATALHA client initialization failed

Error Message

<details about error>
05.081800.40ERRORHA sync error

Error Message

Failed to add HA message, Queue <name>, Headers <message>
05.082100.40ERRORHA network error

Error Message

<number> requests failed in the last minute. The system may require manual intervention.
05.082500.40ERRORHA read error

Error Message

Exception while listening to HA queue: <queue_name>, error <message>
05.083100.30WARNHA connection timeout

Error Message

Failed to connect to AMQP server <host>:<port> switching hosts.
05.083100.40ERRORHA sync timeout

Error Message

Failed connect to AMQP server <host>:<port> retrying in <timeout>
05.083400.40ERRORHA sync write error

Error Message

Could not publish HA message for ‘<endpoint>’.

Host Manager

Event CodeSeverityDescription
02.041500.10DEBUGHost-manager debug communication

Error Message

<message>
02.120501.20INFOHost-manager mode changed to standby

Error Message

The host-manager mode has changed on hostname:<hostname>, host_mode:<standby>, host_status:<host_status>
02.120502.20INFOHost-manager mode changed to run

Error Message

The host-manager mode has changed on hostname:<hostname>, host_mode:<run>, host_status:<host_status>
02.120503.20INFOHost-manager mode changed to shutdown

Error Message

The host-manager mode has changed on hostname:<hostname>, host_mode:<shutdown>, host_status:<host_status>
02.130800.40ERRORUnable to update cluster status in etcd

Error Message

Unable to update cluster status in etcd, this could lead to the HA ring becoming unreliable.
02.180502.20INFOHost-manager status changed to post

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<post>
02.180503.20INFOHost-manager status changed to parsed configuration

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<parsed_conf>
02.180504.20INFOHost-manager status changed to enumerated hardware

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<enum_hardware>
02.180505.20INFOHost-manager status changed to ready

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<ready>
02.180506.20INFOHost-manager status changed to establishing cluster

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<establishing_cluster>
02.180507.20INFOHost-manager status changed to validating cluster

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<validating_cluster>
02.180508.20INFOHost-manager status changed to starting systems

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<starting_systems>
02.180509.20INFOHost-manager status changed to started systems

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<started_systems>
02.180510.40ERRORHost-manager is not responding

Error Message

The host-manager is not responding on hostname:<hostname>, host_mode:<host_mode>, host_status:<not_responding>, network_ips:<network_ips>
02.180511.20INFOHost-manager status changed to running

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<running>
02.180512.20INFOHost-manager status changed to stopping systems

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<stopping_systems>
02.180513.20INFOHost-manager status changed to shutting down

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<shutting_down>
02.180514.20INFOHost-manager status changed to shutdown

Error Message

The host-manager status has changed on hostname:<hostname>, host_mode:<host_mode>, host_status:<shutdown>

Machine Learning (ML)

Event CodeSeverityDescription
08.180503.20INFOML server status changed to starting

Error Message

The ML server status has changed on hostname:<hostname>, host_mode:<host_mode>, ml_status:<starting>
08.180504.20INFOML server status changed to running

Error Message

The ML server status has changed on hostname:<hostname>, host_mode:<host_mode>, ml_status:<running>
08.180505.20INFOML server status changed to stopping

Error Message

The ML server status has changed on hostname:<hostname>, host_mode:<host_mode>, ml_status:<stopping>
08.180506.20INFOML server status changed to stoped

Error Message

The ML server status has changed on hostname:<hostname>, host_mode:<host_mode>, ml_status:<stopped>
08.180507.40ERRORML server has terminated

Error Message

The ML server status has changed on hostname:<hostname>, host_mode:<host_mode>, ml_status:<terminated>

Monitoring

Event CodeSeverityDescription
07.180503.20INFOMonitoring status server status changed to starting

Error Message

The monitoring stats server status has changed on hostname:<hostname>, host_mode:<host_mode>, stats_status:<starting>
07.180504.20INFOMonitoring status server status changed to running

Error Message

The monitoring stats server status has changed on hostname:<hostname>, host_mode:<host_mode>, stats_status:<running>
07.180505.20INFOMonitoring status server status changed to stopping

Error Message

The monitoring stats server status has changed on hostname:<hostname>, host_mode:<host_mode>, stats_status:<stopping>
07.180506.20INFOMonitoring status server status changed to stopped

Error Message

The monitoring stats server status has changed on hostname:<hostname>, host_mode:<host_mode>, stats_status:<stopped>
07.180507.40ERRORMonitoring status server has terminated

Error Message

The monitoring stats server status has changed on hostname:<hostname>, host_mode:<host_mode>, stats_status:<terminated>

Rank Operations

Event CodeSeverityDescription
03.010500.20INFOAdding host to cluster

Error Message

Alter-cluster configuration action: <add_host>, host: <address>
03.010501.20INFOAlter host configuration

Error Message

Alter-cluster configuration action: <alter_host>, host: <address>
03.010502.20INFORemoved host from cluster

Error Message

Alter-cluster configuration action: <remove_host>, host: <address>
03.020501.20INFOAdded rank to cluster

Error Message

The cluster operation: <adding_ranks> has status: <cluster_operation_status>
03.020502.20INFORebalancing data in cluster

Error Message

The cluster operation: <rebalancing> has status: <cluster_operation_status>
03.020503.20INFORemoving rank and rebalancing data

Error Message

The cluster operation: <rebalancing_for_removing_ranks> has status: <cluster_operation_status>
03.020504.20INFORemoving rank from cluster

Error Message

The cluster operation: <removing_ranks> has status: <cluster_operation_status>
03.020505.20INFOChanging the number of ranks in cluster

Error Message

The cluster operation: <resizing_cluster> has status: <cluster_operation_status>
03.020506.20INFOCluster set to backup mode

Error Message

The cluster operation: <backing_up> has status: <cluster_operation_status>
03.020507.20INFOMigrating component

Error Message

The cluster operation: <migrating> has status: <cluster_operation_status>
03.020508.50FATALIrrecoverable error (restart required)

Error Message

The database cluster had an irrecoverable error and must be restarted. Message: <cluster_operation_status>
03.030000.20INFOConfiguration file loaded successfully

Error Message

Configuration file: ‘<gpudb_conf_filename>’ has been successfully loaded.
03.030300.40ERRORConfiguration parameter is invalid

Error Message

<details about parameter>
03.031600.40ERRORRebalance required

Error Message

The following Rank/Tom pairs are not present in the shard list: <rank_tom_list>. A rebalance is necessary to avoid incorrectly distributed data.
03.032200.40ERRORConfiguration file missing

Error Message

Configuration file: ‘<gpudb_conf_filename>’ is missing.
03.032400.40ERRORConfiguration file parse error

Error Message

Unable to parse configuration file: ‘<gpudb_conf_filename>’, msg:<error_msg>
03.033400.40ERRORConfiguration file write error

Error Message

Configuration file: ‘<gpudb_conf_filename>’ is not writable.
03.050800.40ERRORUDF initialization failed

Error Message

Function Environments initialization failed, will be disabled (error: <message>)
03.051600.40ERRORKiFS is not active

Error Message

KiFS not active
03.052500.40ERRORError running startup proc

Error Message

Error decoding execute_proc_request for proc ‘<first>’ to run at startup: <error_msg>
03.060200.30WARNGPU allocation failure

Error Message

GPU allocation limit exceeded when requesting additional: <failure_size> bytes, using CPU fallback allocator.
03.060700.40ERRORGPU device error

Error Message

<details about GPU error>
03.090800.25UERRJob failed

Error Message

Request failed with JobId:<jobid> to: <request_uri>. <error_message>
03.090800.40ERRORJob failed since the system is limited

Error Message

Unable to process request with JobId:<jobid> to: <request_uri>, system is in a limited state. <error_message>
03.090900.25UERRJob processing exception

Error Message

Unable to process credentials for user: <cred_username>, endpoint: <request_uri>, what:<error_msg>
03.091400.25UERRUser impersonation denied for request

Error Message

External user <remote_user> does not have permission to impersonate for endpoint: <request_uri>
03.091700.25UERRInvalid credentials for request

Error Message

Invalid credentials for endpoint: <request_uri>, user: <cred_username>
03.091900.20INFOJob canceled

Error Message

Request canceled with JobId:<jobid> to: <uri>. <error_message>
03.092000.30WARNHTTP request limit reached

Error Message

HTTP request server has reached max number of concurrent and queued connections and is refusing connections. <http_server_info>
03.092600.20INFORank is not accepting jobs

Error Message

Rank is not accepting jobs, rank:<rank>, rank_mode:<rank_mode>, rank_status:<rank_status>, start_count:<start_count>, hostname:<hostname>
03.092700.20INFORank is accepting jobs

Error Message

Rank is accepting jobs, rank:<rank>, rank_mode:<rank_mode>, rank_status:<rank_status>, start_count:<start_count>, hostname:<hostname>
03.093100.30WARNJob times out

Error Message

Job timed out, received: <time>, job_id:<job_id>, endpoint_name:<endpoint_name>, client_ip:<client_ip>, read_table_names:<read_table_names>, write_table_names:<write_table_names>, user_data:<user_data>
03.093200.25UERRRequest unauthorized

Error Message

Invalid or missing credentials for endpoint: <request_uri> <details>
03.093500.25UERRUser is deactivated

Error Message

User not activated for endpoint: <request_uri>, remote user: <remote_user>
03.100800.50FATALLicensed for only a single host

Error Message

License error: <Kinetica Trial Edition limited to a single host> <details>
03.100801.50FATALLicense key GPU limit exceeded

Error Message

License error: <GPU limit exceeded> <details>
03.100802.50FATALLicense key is for different hardware

Error Message

License error: <Licensed for different hardware> <details>
03.100803.50FATALLicense key is for a different machine

Error Message

License error: <Licensed for a different machine> <details>
03.100804.50FATALLicense key memory limit exceeded

Error Message

License error: <Cluster memory limit exceeded> <details>
03.100805.50FATALLicense key has expired

Error Message

License error: <Expired> <details>
03.100806.50FATALLicense key is invalid

Error Message

License error: <Invalid> <details>
03.100807.50FATALLicense key is missing

Error Message

License error: <Missing> <details>
03.100808.50FATALLicence key is not authorized

Error Message

License error: <Unauthorized> <details>
03.110501.20INFOMigration to new host required for component

Error Message

Migration <migration_id> status change, <details>
03.110502.20INFOMigration of component attempting failover to another host

Error Message

Migration <migration_id> status change, <details>
03.110503.20INFOMigrating component to new host

Error Message

Migration <migration_id> status change, <details>
03.110504.20INFOMigrated component to new host successfully

Error Message

Migration <migration_id> status change, <details>
03.110805.40ERRORMigration of component to new host failed

Error Message

Migration <migration_id> failed, <details>
03.120501.20INFORank mode changed to removed

Error Message

The rank mode has been set for rank:<rank>, rank_mode:<removed>, rank_status:<rank_status>, start_count:<start_count>, hostname:<hostname>
03.120502.20INFORank mode changed to stop

Error Message

The rank mode has been set for rank:<rank>, rank_mode:<stop>, rank_status:<rank_status>, start_count:<start_count>, hostname:<hostname>
03.120503.20INFORank mode changed to adding

Error Message

The rank mode has been set for rank:<rank>, rank_mode:<adding>, rank_status:<rank_status>, start_count:<start_count>, hostname:<hostname>
03.120504.20INFORank mode changed to run

Error Message

The rank mode has been set for rank:<rank>, rank_mode:<run>, rank_status:<rank_status>, start_count:<start_count>, hostname:<hostname>
03.140501.20INFOBlocking unsharded ingest before removing rank

Error Message

Removing rank: <rank> on host: <hostname>, status: <block_jobs>
03.140502.20INFOCleared persist of removed rank

Error Message

Removing rank: <rank> on host: <hostname>, status: <persist_cleared>
03.162001.30WARNResource group has reached vram limit

Error Message

Resource group: ‘<name>’ memory limit reached, requested:<amount>, used:<usage>, limit:<limit>
03.162002.30WARNResource group has reached ram limit

Error Message

Resource group: ‘<name>’ memory limit reached, requested:<amount>, used:<usage>, limit:<limit>
03.162003.30WARNResource group has reached disk cache limit

Error Message

Resource group: ‘<name>’ memory limit reached, requested:<amount>, used:<usage>, limit:<limit>
03.162004.30WARNResource group has reached persist limit

Error Message

Resource group: ‘<name>’ memory limit reached, requested:<amount>, used:<usage>, limit:<limit>
03.162005.30WARNResource group has reached cold store limit

Error Message

Resource group: ‘<name>’ memory limit reached, requested:<amount>, used:<usage>, limit:<limit>
03.171500.20INFOSQL request

Error Message

<sql_request>
03.180502.20INFORank status changed to start

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<start>, start_count:<start_count>, hostname:<hostname>
03.180503.20INFORank status changed to post

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<post>, start_count:<start_count>, hostname:<hostname>
03.180504.20INFORank status changed to parsed configuration

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<parsed_conf>, start_count:<start_count>, hostname:<hostname>
03.180505.20INFORank status changed to enumerated hardware

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<enum_hardware>, start_count:<start_count>, hostname:<hostname>
03.180507.20INFORank status changed to starting systems

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<starting_systems>, start_count:<start_count>, hostname:<hostname>
03.180508.20INFORank status changed to started systems

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<started_systems>, start_count:<start_count>, hostname:<hostname>
03.180509.20INFORank status changed to loading data

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<loading_data>, start_count:<start_count>, hostname:<hostname>
03.180510.20INFORank status changed to loaded data

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<loaded_data>, start_count:<start_count>, hostname:<hostname>
03.180511.20INFORank status changed to updating shards

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<updating_shards>, start_count:<start_count>, hostname:<hostname>
03.180512.20INFORank status changed to updated shards

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<updated_shards>, start_count:<start_count>, hostname:<hostname>
03.180513.20INFORank status changed to syncing

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<syncing>, start_count:<start_count>, hostname:<hostname>
03.180514.20INFORank status changed to added rank ready

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<added_rank_ready>, start_count:<start_count>, hostname:<hostname>
03.180515.20INFORank status changed to updating views

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<updating_views>, start_count:<start_count>, hostname:<hostname>
03.180516.20INFORank status changed to updated views

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<updated_views>, start_count:<start_count>, hostname:<hostname>
03.180517.20INFORank status changed to running

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<running>, start_count:<start_count>, hostname:<hostname>
03.180518.40ERRORRank status changed to limited and is unable process requests

Error Message

Rank: <rank> on host: <hostname> is <rank_status>
03.180519.20INFORank status changed to stopped jobs

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<stopped_jobs>, start_count:<start_count>, hostname:<hostname>
03.180520.40ERRORRank status changed to not responding

Error Message

Rank: <rank> on host: <hostname> is <rank_status>
03.180521.20INFORank status changed to shutting down

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<shutting_down>, start_count:<start_count>, hostname:<hostname>
03.180522.20INFORank status changed to shutdown

Error Message

The rank status has been updated for rank:<rank>, rank_mode:<rank_mode>, rank_status:<shutdown>, start_count:<start_count>, hostname:<hostname>
03.180522.40ERRORRank status changed to shutdown due to error

Error Message

Rank: <rank> on host: <hostname> is <rank_status>
03.180523.40ERRORRank status changed to terminated

Error Message

Rank: <rank> on host: <hostname> is <rank_status>
03.190900.40ERRORTable monitor error

Error Message

Unable to prepare and send change notification for table <table_name>. <error_msg>
03.211301.30WARNHigh-water mark eviction cycle in vram tier

Error Message

High-water mark limit reached in tier: <vram>, beginning eviction cycle. current size:<current_size>, high:<high_watermark_size> low:<low_watermark_size>
03.211302.30WARNHigh-water mark eviction cycle in ram tier

Error Message

High-water mark limit reached in tier: <ram>, beginning eviction cycle. current size:<current_size>, high:<high_watermark_size> low:<low_watermark_size>
03.211303.30WARNHigh-water mark eviction cycle in disk cache tier

Error Message

High-water mark limit reached in tier: <disk>, beginning eviction cycle. current size:<current_size>, high:<high_watermark_size> low:<low_watermark_size>
03.211304.30WARNHigh-water mark eviction cycle in persist tier

Error Message

High-water mark limit reached in tier: <persist>, beginning eviction cycle. current size:<current_size>, high:<high_watermark_size> low:<low_watermark_size>
03.211305.30WARNHigh-water mark eviction cycle in cold storage tier

Error Message

High-water mark limit reached in tier: <cold>, beginning eviction cycle. current size:<current_size>, high:<high_watermark_size> low:<low_watermark_size>
03.212004.30WARNPersist tier is full

Error Message

Requested amount exceeds tier capacity, Need: <bytes_needed>, TotalRequested: <bytes_requested>, Avail: <bytes_available>
03.212504.40ERRORPersist file read error

Error Message

Unable to load table data file: ‘<name>‘
03.230800.40ERRORUnable to upgrade table data to current version

Error Message

Error upgrading table <table_name> <reason>

Reveal

Event CodeSeverityDescription
09.180503.20INFOReveal server status changed to starting

Error Message

The reveal server status has changed on hostname:<hostname>, host_mode:<host_mode>, reveal_status:<starting>
09.180504.20INFOReveal server status changed to running

Error Message

The reveal server status has changed on hostname:<hostname>, host_mode:<host_mode>, reveal_status:<running>
09.180505.20INFOReveal server status changed to stopping

Error Message

The reveal server status has changed on hostname:<hostname>, host_mode:<host_mode>, reveal_status:<stopping>
09.180506.20INFOReveal server status changed to stopped

Error Message

The reveal server status has changed on hostname:<hostname>, host_mode:<host_mode>, reveal_status:<stopped>
09.180507.40ERRORReveal server has terminated

Error Message

The reveal server status has changed on hostname:<hostname>, host_mode:<host_mode>, reveal_status:<terminated>

SQL Query Planner

Event CodeSeverityDescription
10.180503.20INFOSQL query planner server status changed to starting

Error Message

The SQL query planner status has changed on hostname:<hostname>, host_mode:<host_mode>, query_planner_status:<starting>
10.180504.20INFOSQL query planner server status changed to running

Error Message

The SQL query planner status has changed on hostname:<hostname>, host_mode:<host_mode>, query_planner_status:<running>
10.180505.20INFOSQL query planner server status changed to stopping

Error Message

The SQL query planner status has changed on hostname:<hostname>, host_mode:<host_mode>, query_planner_status:<stopping>
10.180506.20INFOSQL query planner server status changed to stopped

Error Message

The SQL query planner status has changed on hostname:<hostname>, host_mode:<host_mode>, query_planner_status:<stopped>
10.180507.40ERRORSQL query planner server has terminated

Error Message

The SQL query planner status has changed on hostname:<hostname>, host_mode:<host_mode>, query_planner_status:<terminated>