Skip to content

Commit aa0a550

Browse files
parasebarabernat
andcommitted
Update design-docs/009-tigris-support.md
Co-authored-by: Ryan Abernathey <ryan.abernathey@gmail.com>
1 parent 2f2fd67 commit aa0a550

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

design-docs/009-tigris-support.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,15 +16,19 @@ Tigris has built for us the ability to recover consistency by passing an `X-Tigr
1616
writes and reads are done with the same region in the header, consistency is recovered. We also need `Cache-Control:no-cache`
1717
in the get requests. Of course, this comes at the price of performance, because reads no longer happens from the closest region anywhere in the world.
1818

19-
An alternative would be to set the bucket as region-restricted. In that case all writes and reads go to the single region,
20-
but Icechunk cannot control the bucket configuration.
19+
An alternative would be to set the bucket as region-restricted. In that case all writes and reads go to the single region.
20+
This doesn't work well for Icechunk because:
21+
22+
* It doesn't have access to modifying the bucket configuration
23+
* Users may have other data in their buckets, data they don't want to serve from a single region
24+
* It's not flexible, we lose Tigris benefit of data locality
2125

2226
## What we want
2327

2428
Ideally most of the time users can use Icechunk in the most performant way, at least for reads. Even if it's
2529
slightly unsafe, users will want to make all reads from the closest regions.
2630

27-
By default Icechunk should be perfectly safe and consistency, even at the price of slower performance.
31+
By default Icechunk should be perfectly safe and consistent, even at the price of slower performance.
2832

2933
## How to achieve it
3034

@@ -34,7 +38,7 @@ By default Icechunk should be perfectly safe and consistency, even at the price
3438
* All reads use the `Cache-Control:no-cache` header.
3539
* This will make Icechunk safe, but it will direct all writes and reads to a single region, which may cause performance degradation.
3640

37-
* Setting a `Storage` configuration variable to "`unsafe_use_distributed_reads: True`":
41+
* Setting a `Storage` configuration variable to "`unsafe_read_from_local_region: True`":
3842
* Region is ignored if passed
3943
* No `X-Tigris-Regions` header is passed.
4044
* No `Cache-Control:no-cache` header.

0 commit comments

Comments
 (0)