Looks like DRILL-5547: Linking config options with system option manager ( 
https://github.com/apache/drill/commit/a51c98b8bf210bbe9d3f4018361d937252d1226d 
) introduced a change in the computation, which is based on the number of cores.
https://github.com/apache/drill/blame/6ad9838339999c3e069b6925d0c3ce3077afd8c3/exec/java-exec/src/main/java/org/apache/drill/exec/server/options/TypeValidators.java#L252

Looks like a non-zero value is not being computed. Setting the value as a 
system variable should persist and correct this. Can you file a JIRA for this? 
The fix should be minor.

On 2/21/2018 8:54:53 PM, Arjun kr <arjun...@outlook.com> wrote:
Hi Team,


Did default value for configuration parameter 'planner.width.max_per_node' 
change between Drill 1.10 and 1.11 versions? Also, does default value of 70% of 
total cores still hold true?



-- Drill 1.11


0: jdbc:drill:drillbit=localhost> select * from sys.options where name like 
'%planner.width%';
+------------------------------+-------+-------------------+--------------+----------+----------+-------------+-----------+------------+
| name | kind | accessibleScopes | optionScope | status | num_val | string_val 
| bool_val | float_val |
+------------------------------+-------+-------------------+--------------+----------+----------+-------------+-----------+------------+
| planner.width.max_per_node | LONG | ALL | BOOT | DEFAULT | 0 | null | null | 
null |
| planner.width.max_per_query | LONG | ALL | BOOT | DEFAULT | 1000 | null | 
null | null |
+------------------------------+-------+-------------------+--------------+----------+----------+-------------+-----------+------------+
2 rows selected (0.913 seconds)
0: jdbc:drill:drillbit=localhost>

-Drill 1.10

0: jdbc:drill:schema=dfs> select * from sys.options where name like 
'%planner.width%';
+------------------------------+-------+---------+----------+----------+-------------+-----------+------------+
| name | kind | type | status | num_val | string_val | bool_val | float_val |
+------------------------------+-------+---------+----------+----------+-------------+-----------+------------+
| planner.width.max_per_node | LONG | SYSTEM | DEFAULT | 3 | null | null | null 
|
| planner.width.max_per_query | LONG | SYSTEM | DEFAULT | 1000 | null | null | 
null |
+------------------------------+-------+---------+----------+----------+-------------+-----------+------------+
2 rows selected (0.359 seconds)
0: jdbc:drill:schema=dfs>

Thanks,

Arjun

Reply via email to