You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-3Lines changed: 10 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,13 @@
14
14
* The KCL is designed to process streams from Amazon Kinesis, but by adding the DynamoDB Streams Kinesis Adapter, your application can process DynamoDB Streams instead, seamlessly and efficiently.
15
15
16
16
## Release Notes
17
-
### Latest Release (v1.5.x)
17
+
### Latest Release (v1.5.1)
18
+
* Restores compile compatibility with KCL 1.13.3.
19
+
* Fixes a performance issue that arised when using v1.5.0 with KCL 1.12 through 1.13.2.
20
+
* Fixes a defect where `MaxLeasesForWorker` configuration was not being propagated to `StreamsLeaseTaker`.
21
+
* Finished (SHARD_END) leases will now only be delete after at least 6 hours have passed since the shard was created. This further reduces the chances of lineage replay.
22
+
23
+
### Release (v1.5.0)
18
24
* Introduces the implementation of periodic shard sync in conjunction with Amazon Kinesis Client Library v1.11.x (KCL). The default shard sync strategy is to discover new/child shards only when a consumer completes processing a shard. This default strategy constrains horizontal scaling of customer applications when consuming tables with 10,000+ partitions due to increased DescribeStream calls. Periodic shard sync guarantees that only a subset of the fleet (by default 10) will perform shard syncs, and decouples DescribeStream call volume from growth in fleet size.
19
25
20
26
* Improves inconsistency handling in DescribeStream result aggregation by fixing any parent-open-child-open cases. This ensures that shard sync does not fail due to an assertion failure in KCL on this type of inconsistency.
@@ -24,8 +30,9 @@
24
30
* Introduces `StreamsLeaseTaker` with improved load-balancing of leases among workers.
25
31
* SHARD_END and non-SHARD_END check-pointed leases are balanced independently.
26
32
* Leases are now stolen evenly from other workers instead of from only the most loaded worker. `MaxLeasesToStealAtOneTime` no longer needs to be specified by users. It is now determined automatically based on the number of leases held by the worker. The user-specified value for this is no longer used.
27
-
33
+
28
34
* Users should continue using factory methods from `StreamsWorkerFactory` to create KCL Worker as specified in the guidance of Release v1.4.x.
35
+
* We strongly recommended that you create only one worker per host in your processing fleet to get optimal performance from DynamoDB Streams service.
29
36
30
37
### Release (v1.4.x)
31
38
* This release fixes an issue of high propagation delay of streams records when processing streams on small tables. This issue occurs when KCL ShardSyncer is not discovering new shards due to server side delays in shard creation or in reporting new shard creation to internal services. The code is implemented in a new implementation of IKinesisProxy interface called DynamoDBStreamsProxy which is part of the latest release.
@@ -60,7 +67,7 @@ Add the following to your Maven pom file:
<description>The DynamoDB Streams Adapter implements the AmazonKinesis interface so that your application can use KCL to consume and process data from a DynamoDB stream.</description>
0 commit comments