All,
I tried setting up a SQL Server 2019 BDC on a minikube on my Home PC. I was able to get past some of the errors that came up but now I have this issue of the process not coming out of the BDC deployment process. Am I missing anything?
As you can see, for a long time it is showing **Waiting for control plane to be ready after**
This is what I ran to create the minikube instance "**minikube start --vm-driver "hyperv" --cpus 4 --memory 8192**"
The HomePC is a Dell Alienware machine with 8 logical processors and 32GB RAM.
rgn
D:\minikube>azdata bdc create -c sql2019bdc --accept-eula yes
The privacy statement can be viewed at:
https://go.microsoft.com/fwlink/?LinkId=853010
The license terms for SQL Server Big Data Cluster can be viewed at:
Enterprise: https://go.microsoft.com/fwlink/?linkid=2104292
Standard: https://go.microsoft.com/fwlink/?linkid=2104294
Developer: https://go.microsoft.com/fwlink/?linkid=2104079
Cluster deployment documentation can be viewed at:
https://aka.ms/bdc-deploy
Needed Configuration Values in control.json
Kubernetes Storage Class
- Config Path: spec.storage.data.className
- Description: This indicates the name of the Kubernetes Storage Class to use. You must pre-provision the storage class and the persistent volumes or you can use a built in storage class if the platform you are deploying provides this capability.
- Please provide a value: standard
Kubernetes Storage Class
- Config Path: spec.storage.logs.className
- Description: This indicates the name of the Kubernetes Storage Class to use. You must pre-provision the storage class and the persistent volumes or you can use a built in storage class if the platform you are deploying provides this capability.
- Please provide a value: standard
NOTE: Cluster creation can take a significant amount of time depending on
configuration, network speed, and the number of nodes in the cluster.
Starting cluster deployment.
Waiting for cluster controller to start.
Waiting for cluster controller to start.
Waiting for cluster controller to start.
Waiting for cluster controller to start.
Cluster controller endpoint is available at 172.17.YY.XX:30080.
Waiting for control plane to be ready after 5 minutes.
Waiting for control plane to be ready after 10 minutes.
Waiting for control plane to be ready after 15 minutes.
Waiting for control plane to be ready after 20 minutes.
Waiting for control plane to be ready after 25 minutes.
Waiting for control plane to be ready after 30 minutes.
Waiting for control plane to be ready after 35 minutes.
Waiting for control plane to be ready after 40 minutes.
Waiting for control plane to be ready after 45 minutes.
Waiting for control plane to be ready after 50 minutes.
Waiting for control plane to be ready after 55 minutes.
Waiting for control plane to be ready after 60 minutes.
Waiting for control plane to be ready after 65 minutes.
Waiting for control plane to be ready after 70 minutes.
Waiting for control plane to be ready after 75 minutes.
Waiting for control plane to be ready after 80 minutes.
Waiting for control plane to be ready after 85 minutes.
Waiting for control plane to be ready after 90 minutes.
Waiting for control plane to be ready after 95 minutes.
Waiting for control plane to be ready after 100 minutes.
Waiting for control plane to be ready after 105 minutes.Below is bdc.json file:
{
"apiVersion": "v1",
"metadata": {
"kind": "BigDataCluster",
"name": "sql2019bdc"
},
"spec": {
"resources": {
"nmnode-0": {
"spec": {
"replicas": 1
}
},
"sparkhead": {
"spec": {
"replicas": 1
}
},
"zookeeper": {
"spec": {
"replicas": 0
}
},
"gateway": {
"spec": {
"replicas": 1,
"endpoints": [
{
"name": "Knox",
"serviceType": "NodePort",
"port": 30443
}
]
}
},
"appproxy": {
"spec": {
"replicas": 1,
"endpoints": [
{
"name": "AppServiceProxy",
"serviceType": "NodePort",
"port": 30778
}
]
}
},
"master": {
"metadata": {
"kind": "Pool",
"name": "default"
},
"spec": {
"type": "Master",
"replicas": 1,
"endpoints": [
{
"name": "Master",
"serviceType": "NodePort",
"port": 31433
}
],
"settings": {
"sql": {
"hadr.enabled": "false"
}
}
}
},
"compute-0": {
"metadata": {
"kind": "Pool",
"name": "default"
},
"spec": {
"type": "Compute",
"replicas": 1
}
},
"data-0": {
"metadata": {
"kind": "Pool",
"name": "default"
},
"spec": {
"type": "Data",
"replicas": 2
}
},
"storage-0": {
"metadata": {
"kind": "Pool",
"name": "default"
},
"spec": {
"type": "Storage",
"replicas": 2,
"settings": {
"spark": {
"includeSpark": "true"
}
}
}
}
},
"services": {
"sql": {
"resources": [
"master",
"compute-0",
"data-0",
"storage-0"
]
},
"hdfs": {
"resources": [
"nmnode-0",
"zookeeper",
"storage-0",
"sparkhead"
],
"settings": {}
},
"spark": {
"resources": [
"sparkhead",
"storage-0"
],
"settings": {
"spark-defaults-conf.spark.driver.cores": "1",
"spark-defaults-conf.spark.driver.memory": "1664m",
"spark-defaults-conf.spark.driver.memoryOverhead": "384",
"spark-defaults-conf.spark.executor.instances": "1",
"spark-defaults-conf.spark.executor.cores": "2",
"spark-defaults-conf.spark.executor.memory": "3712m",
"spark-defaults-conf.spark.executor.memoryOverhead": "384",
"yarn-site.yarn.nodemanager.resource.memory-mb": "12288",
"yarn-site.yarn.nodemanager.resource.cpu-vcores": "6",
"yarn-site.yarn.scheduler.maximum-allocation-mb": "12288",
"yarn-site.yarn.scheduler.maximum-allocation-vcores": "6",
"yarn-site.yarn.scheduler.capacity.maximum-am-resource-percent": "0.34"
}
}
}
}
}
Below is control.json file:
{
"apiVersion": "v1",
"metadata": {
"kind": "Cluster",
"name": "mssql-cluster"
},
"spec": {
"docker": {
"registry": "mcr.microsoft.com",
"repository": "mssql/bdc",
"imageTag": "2019-CU4-ubuntu-16.04",
"imagePullPolicy": "Always"
},
"storage": {
"data": {
"className": "",
"accessMode": "ReadWriteOnce",
"size": "15Gi"
},
"logs": {
"className": "",
"accessMode": "ReadWriteOnce",
"size": "10Gi"
}
},
"endpoints": [
{
"name": "Controller",
"serviceType": "NodePort",
"port": 30080
},
{
"name": "ServiceProxy",
"serviceType": "NodePort",
"port": 30777
}
],
"settings": {
"controller": {
"logs.rotation.size": "5000",
"logs.rotation.days": "7"
}
}
}
}