Just an update, to round this out. We investigated further internally, and found that although we have a cleanup process in place to remove the internal repos that are being checked out for workflows, it was failing to catch up due to the sheer volum...
Hi, @Priscilla Maynard -- can you please send an email to help@databricks.com with more details? Thanks.@Kit Yam Tse -- we are checking this internally, and will keep you posted. Thanks for reporting this.
Just to clarify: we count both internal (from workflows, among others) and workspace repos to the 5K count. For workflows where the repos count are exceeded, execution is blocked initially for 10 minutes until the count is reduced. There is a cleanup...
Can you try:databricks clusters restart --cluster-id <the-cluster-id>$ databricks clusters restart --help
Usage: databricks clusters restart [OPTIONS]
Restarts a Databricks cluster given its ID.
If the cluster is not currently in a RUNNING st...
