Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graceful handling and recovery for QuotaExceededError #317

Open
fl0rek opened this issue Jul 2, 2024 · 1 comment
Open

Graceful handling and recovery for QuotaExceededError #317

fl0rek opened this issue Jul 2, 2024 · 1 comment

Comments

@fl0rek
Copy link
Member

fl0rek commented Jul 2, 2024

Context

Browsers use quotas to limit the amount of data page can store locally, see mdn for details.

Available quota can be queried with StorageManager

Issue

When transaction which would put us above the quota is commited, QuotaExceededError is returned and transaction is rolled back. From this point on, Indexeddb is in read-only state until restart (note that this by itself doesn't change the quota, and db can lock up again, if quota is exceeded).

From the user perspective, node just stops syncing (as all the db inserts fail).

@zvolin
Copy link
Member

zvolin commented Oct 8, 2024

from sync discussion:

  • this is kinda similar to no space left on device error, we can't handle it really
  • but we can document it
  • and allow configuring the syncing window period

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants