SPICE dataset capacity does not decrease after data removal

Q&A
,
1

I’m encountering an issue with SPICE capacity usage.

I created a dataset using the new dataset creation UI and imported data into SPICE (approximately 50 GB). Later, I reduced the data selection and eventually deleted the dataset. However, the SPICE usage shown in the Admin console did not decrease. It remains the same and now indicates over-capacity.

I also checked all datasets through the AWS console to verify SPICE usage, but the total usage still does not align with the reported capacity in the Admin view.

  1. Is this behavior expected when using the new dataset experience?
  2. How can I accurately identify which datasets are consuming SPICE capacity?
  3. Is there any known delay or issue related to SPICE capacity recalculation?

I’ve seen several similar cases in the Q&A, but there doesn’t seem to be a solid solution other than opening a case with AWS Support. In the meantime, while waiting for AWS to respond to my case, any guidance on how to properly manage and reclaim SPICE capacity in this scenario would be greatly appreciated.
Thank you.

2

Hi @nugrah.salim,

Welcome to the Quick Suite Community! That is definitely interesting behavior that the SPICE usage is indicating over-capacity despite you deleting a dataset. As this is dealing with your private account, we cannot specifically help in this matter, but it is great that you are already in contact with AWS Support (as they can potentially help you better in this scenario).

My guess is that the UI is displaying one number but the actual capacity could be different internally.

3

Hi Luis, Thank you for your response!

I’d like to share a few additional observations that might help clarify what’s happening with the SPICE capacity issue:

  1. Legacy datasets:
    Even though the account shows as over capacity, sometimes legacy datasets (created with the old dataset experience) can still be refreshed successfully. However, after some time, the refresh will fail with an error saying:

    ACCOUNT_CAPACITY_LIMIT_EXCEEDED

    The data being ingested exceeds the current capacity on your account. Either purchase more SPICE capacity or delete unnecessary datasets to free up space.

  2. New dataset experience:
    When I try to create or refresh a dataset using the new dataset UI, it fails immediately, even after I applied the same steps above (adding 1 GB, deleting datasets, etc.).

It seems like there might be a mismatch between the SPICE capacity shown in the UI and the actual internal usage, especially for accounts using the new dataset experience.

Thanks again for your time and help!

1 Like
4

Hi @nugrah.salim,

Just checking back in since it’s been a while since last communication. Were you able to receive a response from AWS Support regarding this question? If so, please feel free to share as this could definitely be helpful to other users running into similar behavior!

Thank you!

5

Yes, there was a response and they resolved my problem: they found some unreleased SPICE tables and have now released them. They resolved the issue on their backend, and if I encounter the same problem again, I will need to submit another request.

1 Like