Vertica sets the spread timeout period to 8 seconds when the IP addresses of all cluster nodes start with the same two bytes. Otherwise, Vertica sets the spread timeout period to 25 seconds.
When you know your network or nodes may be unable to respond for a specific amount of time, you can increase the spread timeout period to longer than this time using the SET_SPREAD_OPTION function.
The SET_SPREAD_OPTION function is avaiable starting in Vertica 9.2.1-0.
Example:
dbadmin=> SELECT SET_SPREAD_OPTION( 'TokenTimeout', '16000');
NOTICE 9003: Spread has been notified about the change
SET_SPREAD_OPTION
--------------------------------------------------------
Spread option 'TokenTimeout' has been set to '16000'.
(1 row)
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
Have fun!
Related Posts:
Min and Max Values for Spread Daemon Timeout
Set the Spread Daemon Timeout Back to Default Value
Monitor the Current Value of Node Spread Daemon Timeouts
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!
