Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

How to delete event streams properly

We had some tests with the Activator and event streams to detect new file creations in the Azure Blob container. However, even after deleting the items and had deleted the Event Grid System Topic in ...
Eventstream
  • v-csrikanth's avatar
    v-csrikanth
    1 year ago

    Hi Anonymous 

    Even after you delete the Azure Event Grid topic, the Event Stream and Activator objects you created in Fabric continue to run in the background until they’re removed from the workspace.
    To fully terminate them and free up your capacity:

    1. In the Fabric portal, open your workspace and go to Data Factory → Event streams. Find each stream (for example “Test001” or “BLOB_EVENT_MONITOR”), click the ellipsis next to its name, and choose Delete.

    2. Still under Data Factory, switch to Activators, locate “BLOB_EVENT_ACTIVATOR,” click the ellipsis, and select Delete.

    3. Wait five to ten minutes for Fabric to shut down the background processes, then refresh your Capacity Monitor; the CU and Duration figures for those items should drop to zero.

    4. (Optional workaorund) In the Azure portal, delete the corresponding Event Grid System Topic and any related subscriptions to stop any remaining events from reaching Fabric.

    Once both the Event Stream and Activator definitions are removed from Fabric—and the Azure topic/subscription is deleted—the Capacity Monitor will no longer list or bill for those executions.

    If this resolves your issue, please give us Kudos and mark this response as Accepted as solution.
    Best regards,
    Community Support Team _ C Srikanth.

  • v-csrikanth's avatar
    v-csrikanth
    1 year ago

    Hi Anonymous 
    Thanks for reaching out to Fabric Community.
    As you confirmed that you reached to the support for the resolving the issue. If you are facing any new issue can you mark the post as resolved. 

    If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
    Looking forward to your reply!


    Best Regards,
    Community Support Team _ C Srikanth.

v-csrikanth's avatar
v-csrikanth
Community Support
1 year ago

HI Anonymous 

It's been a while since I heard back from you and I wanted to follow up. Have you had a chance to try the solutions that have been offered?
If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

Best Regards,
Community Support Team _ C Srikanth.

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Hi Csrikanth,
Thanks for sharing the deletion steps. When I deleted the items, I recall deleting the first EventStream which was called test001 and deleted right after it was created successfully.   Then I had created one EventStream and one Activator in the Dev Workspace. When I identified the capacity issue, I deleted the EventStream first, followed by the Fabric Activator. However, I didn’t wait for 5 minutes between each step. It appears that these background items were still running. After identifying this, I attempted to delete the items in the Azure Event Grid Subscription, but unfortunately, it didn’t resolve the issue. The background event listener is still active and consuming Fabric capacity. We’ve already reached out to Microsoft Support regarding this matter. Thanks for following up on this. It would be really helpful if the deletion steps could be included in an official Microsoft document for future reference.
 
Best regards,
Sandra