[IGNITE-13183] Query timeout redesign

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.10
• Component/s: sql
• Release Note: Adds ability to set up default query timeout for the all nodes of the cluster
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Taras Ledkov
• Reporter: Taras Ledkov
• Created: 25/Jun/20 13:28
• Updated: 18/Aug/20 20:50
• Resolved: 18/Aug/20 20:50

Description

Motivation:
Now the query timeout is set up for each node separately by the node configuration. This property isn't propagated for the all nodes of cluster. Also user cannot change / disable query timeout without restart all nodes of the cluster.

Proposal fix:

• Adds the default query timeout property to the DistributedSqlConfiguration. Use distributed metastore to store and manage the property.
• Deprecates the SqlConfiguration#defaultQueryTimeout property and use it to set up initial value of new property DistributedSqlConfiguration#defaultQueryTimeout
• Adds info about explicit query timeout to GridH2QueryRequest (boolean flag explicitTimeout=false by default). This is necessary so that the default timeout may be used for queries from old nodes.
• When query timeout is set to zero by old node (explicitTimeout=false) we assume this is the default value and use default timeout for this queries.

Issue Links

• relates to: IGNITE-13186 Commands for control.sh to manage properties at the distributed metastore
• links to: GitHub Pull Request #8107
• links to: TCBot