Can read ADX (free tier) from Databricks but cannot write rows to ADX about azure-kusto-spark HOT 4 CLOSED

We need more details - Are there any errors raised?

Run ".show ingestion failures" on your cluster and see if errors pop up.

Also, the default ingestion policy batches the data for a few minutes before ingesting it and the connector waits for the ingestion to complete (by default).
Try running it with a shorter ingestion batching policy - https://learn.microsoft.com/en-us/azure/data-explorer/kusto/management/batchingpolicy

from azure-kusto-spark.

Thank you for the troubleshooting steps. Apparently this is a resource issue on the free tier ADX.

The cluster has reached its full data capacity of 10,468,982,784 bytes, to ingest more data please reduce the data size by either deleting some of the data or adjusting the retention policy.

I thought (based on this page) that the limit was 100 GB, but in any case, the issue is not with the connector.

I appreciate the guidance on the batching too.

from azure-kusto-spark.

One thing that can be related to the connector and if your cluster is low on resources its worth considering - the connector can create leftovers which are supposed to be cleaned at the end of each run - if not they are auto-cleaned by the service after a week (this can happen if a 'write' run is canceled before fully waited). Read here about stagingResourcesAutoCleanupTimeout
https://github.com/Azure/azure-kusto-spark/blob/master/docs/KustoSink.md

This cannot happen in the connector 'Queued' mode.

from azure-kusto-spark.

Would this be the "on demand" equivalent of the staging resources auto cleanup? This seems to trigger an IndependentGarbageCollectionRequested in the cluster.

.clean databases extentcontainers

from azure-kusto-spark.