-
Cluster Termination:
- As a Community Edition user, your cluster will automatically terminate after an idle period of two hours. If your cluster has been inactive for a while, it might have terminated. You can check the event logs to verify this.
- To refresh the event logs, follow these steps:
- Go to the Clusters tab in your Databricks workspace.
- Locate the cluster youโre having trouble with.
- Click on the cluster name to view its details.
- Look for the Event Logs section and click the Refresh button.
- If the cluster has indeed terminated, youโll need to create a new one.
-
Bootstrap Timeout:
- The error message you received indicates a node daemon ping timeout. This could be due to network connectivity issues between the data plane and the control plane.
- Here are some steps to troubleshoot this:
- Ensure that the network configuration is correct. Check if there are any firewalls, security groups, or network ACLs blocking communication between the nodes.
- Verify that the private IP address of the instance (i-0943508bf00d6e86f) is reachable from the control plane.
- Check if there are any DNS resolution issues that might prevent proper communication.
- If youโre using a VPC peering setup, make sure itโs correctly configured.
- Consider running a traceroute or ping from the control plane to the data plane to identify any network bottlenecks.
-
Cluster Creation:
- If the above steps donโt resolve the issue, try creating a new cluster. Sometimes, starting fresh can help overcome any underlying issues.
- Remember that the Community Edition has limitations, so consider upgrading to a paid subscription for more configuration options.
Feel free to provide additional details or ask further questions, and weโll work together to get your cluster up and running! ๐
