SYMPTOMS
The following failure message appears in the engine or debug logs or within AtScale as the result of a batch or query failure: Timed out after total timeout [5 hours], queued for [None], with message [Timed out by master timeout control]
ROOT CAUSE
An Aggregate and/or UDA creation is hitting a 5-hour timeout set by the connection.pool.maxTimeout engine setting. This hard limit is the maximum amount of time a connection can be leased before it is closed, regardless of progress made on the leased connection.
RESOLUTION
If the query takes a relatively long time to process, you can increase the connection.pool.maxTimeout to a higher value from the default value of 5.hours. Depending also on the SQL Engine configuration setting in AtScale, you may need to provide JDBC parameters to help improve performance; however, this will depend on input from our Professional Services team or the respective Hadoop provider Support team.