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
About the Author
James Knicely
Vertica Field Chief Technologist
I've had the privilege of working with many database technologies in my career. But after being introduced to Vertica in May of 2011 as a client, I was hooked on the new technology after witnessing a query run in milliseconds that had previously ran for hours on the legacy database we had in place. It was then that I knew I wanted to eventually join the Vertica team, and 4 years later I did! I am currently a Vertica evangelist and am ready to help you get on board! Please feel free to reach out to me with any questions you have about Vertica and make sure to follow my Vertica Quick Tips!
