Improve snapshot rollback failure when snapshots produced too frequent.
See original GitHub issueHi all, I am seeing the error below.
java.lang.IllegalArgumentException: [BUG] Expected sorted snapshot log entries.
at org.apache.iceberg.relocated.com.google.common.base.Preconditions.checkArgument(Preconditions.java:142)
at org.apache.iceberg.TableMetadata.<init>(TableMetadata.java:306)
at org.apache.iceberg.TableMetadata$Builder.build(TableMetadata.java:1040)
Does it mean we shouldn’t write the new snapshot too frequent (within a minute)? I wonder should an improvement be added to the writer side to prevent such error happen? https://github.com/apache/iceberg/blob/master/core/src/main/java/org/apache/iceberg/TableMetadata.java#L310
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Best practices for persistent disk snapshots - Google Cloud
As a best practice, take a snapshot of the disk once per hour. Avoid taking snapshots more often than that. The easiest way...
Read more >ORA-01555 Snapshot Too Old - Burleson Consulting
Cause: Rollback records needed by a reader for consistent read are overwritten by other writers. Action: If in Automatic Undo Management mode, increase...
Read more >Performance impact of snapshots in VMware vSphere 7
As you know, snapshots affect the performance of virtual machines (VMs) in your VMware environment. The performance is affected by how long ...
Read more >Failed to snapshot shard - how to solve related issues - Opster
It is better to use Elasticsearch snapshots instead of disk backups/snapshots. An index must be closed in order to be restored. Another option...
Read more >Restore a snapshot | Elasticsearch Guide [8.5] | Elastic
This guide shows you how to restore a snapshot. Snapshots are a convenient way to store a copy of your data outside of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jpugliesi there is no workaround for this. However, I believe a 0.13.2 release is planned soon, which will have the fix for this. If you need the fix sooner, you can build Iceberg from the 0.13.x branch yourself.
I can confirm the fix is working for 0.13.x branch. So I am closing this diff. cc: @SinghAsDev