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

[bug]: Exporting with foundationdb fails #520

Open
1 task done
swerter opened this issue Jun 7, 2024 · 3 comments
Open
1 task done

[bug]: Exporting with foundationdb fails #520

swerter opened this issue Jun 7, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@swerter
Copy link

swerter commented Jun 7, 2024

What happened?

When exporting the whole database, foundationdb complains that the transaction is too old:

./stalwart-mail --config=/usr/local/etc/stalwart/config.toml  --export /opt/stalwart-mail/export
Exporting database to /opt/stalwart-mail/export/property.
Exporting database to /opt/stalwart-mail/export/acl.
Exporting database to /opt/stalwart-mail/export/fts_index.
Exporting database to /opt/stalwart-mail/export/queue.
Exporting database to /opt/stalwart-mail/export/config.
Exporting database to /opt/stalwart-mail/export/directory.
Exporting database to /opt/stalwart-mail/export/blob.
Exporting database to /opt/stalwart-mail/export/log.
Exporting database to /opt/stalwart-mail/export/bitmap.
Exporting database to /opt/stalwart-mail/export/lookup.
Exporting database to /opt/stalwart-mail/export/index.
Failed to iterate over data store: Internal Error: FoundationDB error: Transaction is too old to perform reads or be committed

Anything else I can provide you with?

The setup is pretty standard:

directory.internal.cache.entries = 500
directory.internal.store = "foundationdb"
directory.internal.type = "internal"
store.foundationdb.compression = "lz4"
store.foundationdb.purge.frequency = "0 3 *"
store.foundationdb.type = "foundationdb"

Thanks a lot for your help.

How can we reproduce the problem?

I can reproduce the problem by doing the following steps:

Version

v0.7.x

What database are you using?

FoundationDB

What blob storage are you using?

S3-compatible

Where is your directory located?

Internal

What operating system are you using?

None

Relevant log output

./stalwart-mail --config=/usr/local/etc/stalwart/config.toml  --export /opt/stalwart-mail/export
Exporting database to /opt/stalwart-mail/export/property.
Exporting database to /opt/stalwart-mail/export/acl.
Exporting database to /opt/stalwart-mail/export/fts_index.
Exporting database to /opt/stalwart-mail/export/queue.
Exporting database to /opt/stalwart-mail/export/config.
Exporting database to /opt/stalwart-mail/export/directory.
Exporting database to /opt/stalwart-mail/export/blob.
Exporting database to /opt/stalwart-mail/export/log.
Exporting database to /opt/stalwart-mail/export/bitmap.
Exporting database to /opt/stalwart-mail/export/lookup.
Exporting database to /opt/stalwart-mail/export/index.
Failed to iterate over data store: Internal Error: FoundationDB error: Transaction is too old to perform reads or be committed

Code of Conduct

  • I agree to follow this project's Code of Conduct
@swerter swerter added the bug Something isn't working label Jun 7, 2024
@mdecimus
Copy link
Member

Thanks, a fix for this is going to be included in version 0.8.3.

@swerter
Copy link
Author

swerter commented Jun 14, 2024

Fantastic, thanks a lot!

@swerter swerter closed this as completed Jun 14, 2024
@mdecimus
Copy link
Member

I'll leave it open to track the issue.

@mdecimus mdecimus reopened this Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants