kube-apiserver.yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube-apiserver port: 30009 Get server log List all server pods: kubectl get po Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

kube-apiserver.yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube-apiserver port: 30009 Get server log List all server pods: kubectl get po Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

kube-apiserver.yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube-apiserver port: 30009 Get server log List all server pods: kubectl get po Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

kube-apiserver.yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube-apiserver port: 30009 Get server log List all server pods: kubectl get po Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube- apiserver port: 30009 Get server log List all server pods: kubectl get po Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube- apiserver port: 30009 Get server log List all server pods: kubectl get po Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube- apiserver port: 30009 Get server log List all server pods: kubectl get po Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube- apiserver port: 30009 Get server log List all server pods: kubectl get Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

yaml (usually under path: /etc/kubernetes/manifests/) # add or change line 'service-node-port-range=1-32767' under kube- apiserver port: 30009 Get server log List all server pods: kubectl get Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where

Allocation Resources for a single executor, such as CPUs and memory, can be fixed size. So, the range [minExecutors, maxExecutors] determines how many recourses the engine can take from the cluster manager value is the larger, the better, to handle heavier queries. However, we must limit it to a reasonable range in terms of the entire cluster’s resources. Otherwise, a large query may trigger the engine where row selected (0.039 seconds) 0: jdbc:hive2://localhost:10009/> select /*+ REPARTITION(5) */ * from range(1, 10); +-----+ | id | +-----+ | 2 | | 6 | | 7 | (continues on next page) 52 Chapter 3. What’s