Adjusting Spread Daemon Timeouts for Virtual Environments

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

Spread Daemon Timeout
If you are running Vertica in a virtual environment, you’ve probably seen nodes leave the cluster even though they are still running. If network delays or temporary pauses of a VM last longer than the spread timeout period, you may see up nodes leave the database. In these cases, you can increase the spread timeout to reduce or eliminate instances where up nodes leave the database.

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