Monitor the Current Value of Node Spread Daemon Timeouts

Posted May 24, 2019 by Jim Knicely, Vertica Principal Solution Architect

Spread Daemon Timeout
When you know your network or nodes may be unable to respond for a specific amount of time due to network delays or temporary pauses of a VM, you can increase the spread timeout period to longer than this time using the SET_SPREAD_OPTION function (available starting in Vertica 9.2.1-0).

You can view the current value of the Spread Daemon timeout for each cluster node in the SPREAD_STATE system table.

Example: dbadmin=> SELECT * FROM spread_state; node_name | token_timeout --------------------+--------------- v_test_db_node0001 | 8000 v_test_db_node0002 | 8000 v_test_db_node0003 | 8000 (3 rows) dbadmin=> SELECT SET_SPREAD_OPTION( 'TokenTimeout', '32000'); NOTICE 9003: Spread has been notified about the change SET_SPREAD_OPTION -------------------------------------------------------- Spread option 'TokenTimeout' has been set to '32000'. (1 row) dbadmin=> SELECT * FROM spread_state; node_name | token_timeout --------------------+--------------- v_test_db_node0001 | 32000 v_test_db_node0002 | 32000 v_test_db_node0003 | 32000 (3 rows) Helpful Links:

https://www.vertica.com/docs/latest/HTML/Content/Authoring/UsingVerticaOnAzure/AdjustingSpreadDaemonTimeouts.htm https://www.vertica.com/docs/latest/HTML/Content/Authoring/SQLReferenceManual/Functions/VerticaFunctions/SET_SPREAD_OPTION.htm https://www.vertica.com/docs/latest/HTML/Content/Authoring/SQLReferenceManual/SystemTables/MONITOR/SPREAD_STATE.htm

Have fun!

Related Posts:
Adjusting Spread Daemon Timeouts for Virtual Environments
Min and Max Values for Spread Daemon Timeout
Set the Spread Daemon Timeout Back to Default Value