This topic discusses Kubernetes troubleshooting scenarios as they pertain to Azure AKS and Amazon EKS environments.
Why are my edits to files in the config directory not being applied?
I’m making changes to the configuration files in the config directory, but the changes are not showing up on the pods.
The config directory cannot have any binary files.
In the process of deployment, the contents of the config directory are copied to all the pods at the /opt/dremio/conf location, and then the configmap is created and made available on the pod.
If binary files exist in the config directory, then the creation of the configmap fails.
Ensure that there are no binary files in the config directory and re-deploy.
Why are my pods still not being provisioned for lack of CPU/memory?
I asked for 5 executors and have 5 nodes in my Kubernetes cluster that should be able to satisfy the CPU/memory requirements, but I’m still running into lack of CPU/Memory issues.
Along with the executor pods, the deployment also creates the following pods which need to be accounted for when calculating CPU/memory requirements for the Dremio cluster.
- Dremio master-coordinator pod (requires an allocated node)
- Zookeeper pods (requires a small amount of resources)
The number of allocated nodes in the cluster must be equivalent to the number of Dremio executors plus one (1) for the Dremio master-coordinator.
Allocate an additional node (1 node) in the cluster for the Dremio master-coordinator pod.
Why is data from an old deployment still around?
I deleted my Dremio deployment (
helm delete <helm-release>),
but when I install a new release, data from the old deployment is still around.
The helm chart uses scalesets for Dremio pods. In Kubernetes, any associated persistent volume with a pod in a scaleset is not deleted when you delete the scaleset.
To completely delete the data, you need to delete the persistent volumes. For example:
kubectl get pvc kubectl delete pvc dremio-master-volume-dremio-master-0