Description
📝 Scenario
As a FinOps hub admin, I need to start the ADX cluster in order to ingest data when the cluster is shut down
💎 Solution
When ingestion_ExecuteETL
runs, if the ADX cluster isn't started, it will run for ~8 hours before it fails, then it needs to be manually rerun. This causes ingestion delays and extra charges for pipeline runs that don't actually ingest any data.
Instead, check if the cluster is started and start it, if needed. Starting a cluster can take 30-45m, so investigate options to re-schedule the ingestion run so the pipeline doesn't wait and incur charges during that time.
📋 Tasks
### Required tasks
- [ ] Update ingestion_ExecuteETL to start the ADX cluster if not started
- [ ] Document the behavior in the data processing docD
### Stretch goals
- [ ] TODO: Add tasks
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Leave comments to help us solidify the vision.
Activity
Check ADX cluster run status in datafactory.bicep feature #1371
Update data-processing.md
Update data processing documentation to reflect changes for #1371 (#1590
#1371 dataFactory.bicep
implementing requested feature [Hubs] Start the ADX cluster when shut…
implementing changes for issue: [Hubs] Start the ADX cluster when shu…
changelog update to document changes to fix [Hubs] Start the ADX clus…