The data folder that will be used for storing deployed SQL data stores.
How many threads will be allocated for serving requests in Thrift's ThreadPoolServer
Whether this DNode should find the next available port in case "dnode.port" is busy or fail otherwise.
The amount of seconds that the DNode will cache SQL connection pools. After that time, it will close them. Remember
that the DNode may receive requests for different versions in the middle of a deployment, so that's why we want to
expire connection pools after some time (to not cache connection pools that will not be used anymore).
The amount of seconds that the DNode will wait before canceling a too-long deployment.
A hard limit on the number of results per each SQL query that this DNode may send back to QNodes.
If set, this DNode will listen for test commands. This property is used to activate responsiveness to some commands
that are useful for integration testing: making a DNode shutdown, etc.
Number of SQL connection pools that will be cached. There will be one SQL connection pool for each tablespace,
version and partition that this DNode serves. So this number must not be smaller than the different numbers of
tablespace + version + partitions.
In milliseconds, queries that are slower will be logged with a WARNING.
Queries that run for more than this time will be interrupted.