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

feat: recover database on commit timestamp conflict #229

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

agaffney
Copy link
Contributor

@agaffney agaffney commented Nov 11, 2024

Closes #219

@agaffney
Copy link
Contributor Author

agaffney commented Nov 11, 2024

{"time":"2024-11-11T17:35:32.86448942-06:00","level":"WARN","msg":"database initialization error","error":"commit timestamp mismatch: 1731367833995 (metadata) != 1731367833990 (blob)","component":"ledger"}
{"time":"2024-11-11T17:35:32.87324437-06:00","level":"INFO","msg":"chain rolled back, new tip: 218023cc08a9a31c0db1ab76b5142bfa0db7f0f272942a1305ec0190ecc658bf at slot 2040","component":"ledger"}

@agaffney agaffney force-pushed the feat/db-conflict-recover branch from 836418e to 39993ca Compare November 11, 2024 23:35
@agaffney agaffney merged commit 1ebce4c into main Nov 11, 2024
6 checks passed
@agaffney agaffney deleted the feat/db-conflict-recover branch November 11, 2024 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve database commit timestamp mismatch handling
2 participants