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.

Sign up for GitHub

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

Jump to bottom

Documentation: added <pre> tags so fixed-format diagrams aren't gar… #1058

Merged
merged 1 commit into from
Mar 7, 2023
Merged

Documentation: added <pre> tags so fixed-format diagrams aren't gar… #1058

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 8 additions & 10 deletions ...-kinesis-client/src/main/java/software/amazon/kinesis/leases/HierarchicalShardSyncer.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -855,22 +855,20 @@ static class NonEmptyLeaseTableSynchronizer implements LeaseSynchronizer {
* * the parent shard has expired.
* <p>
* For example:
* <pre>
* Shard structure (each level depicts a stream segment):
* 0 1 2 3 4 5 - shards till epoch 102
* \ / \ / | |
* 6 7 4 5 - shards from epoch 103 - 205
* \ / | / \
* 8 4 9 10 - shards from epoch 206 (open - no ending sequenceNumber)
*
* Current leases: (4, 5, 7)
*
* If initial position is LATEST:
* - New leases to create: (6)
* If initial position is TRIM_HORIZON:
* - New leases to create: (0, 1)
* If initial position is AT_TIMESTAMP(epoch=200):
* - New leases to create: (0, 1)
*
* </pre>
* Assuming current leases are (4, 5, 7), new leases to create for an initial position are:
* <ul>
* <li>LATEST: (6)</li>
* <li>TRIM_HORIZON: (0, 1)</li>
* <li>AT_TIMESTAMP(epoch=200): (0, 1)</li>
* </ul>
* <p>
* The leases returned are sorted by the starting sequence number - following the same order
* when persisting the leases in DynamoDB will ensure that we recover gracefully if we fail
Expand Down
Loading