Releases: pingcap/tiflow
Releases · pingcap/tiflow
ticdc v4.0.13
Improvements
- Implement the processor flow control to avoid memory overflow (OOM) #1751
- Support cleaning up stale temporary files in Unified Sorter and prevent multiple
cdc server
instances from sharing the samesort-dir
directory #1741 - Add the HTTP handler for the failpoint #1732
Bug Fixes
- Fix the deadlock issue caused by the flow control when the sorter's input channel has been blocked #1779
- Fix the issue that the TiKV GC safe point is blocked due to the stagnation of TiCDC changefeed checkpoint #1756
- Revert the update in
explicit_defaults_for_timestamp
which requires theSUPER
privilege when replicating data to MySQL #1749
ticdc v5.0.1
Bug Fixes
- Fix the concurrency issue in Unified Sorter and filter the unhelpful error messages #1678
- Fix a bug that the creation of redundant directories might interrupt the replication with MinIO #1672
- Set the default value of the
explicit_defaults_for_timestamp
session variable toON
to make the MySQL 5.7 downstream keep the same behavior with the upstream TiDB #1659 - Fix the issue that the incorrect handling of
io.EOF
might cause replication interruption #1648 - Correct the TiKV CDC endpoint CPU metric in the TiCDC dashboard #1645
- Increase
defaultBufferChanSize
to avoid replication blocking in some cases #1632
ticdc v5.0.0
Improvements
- Add a double confirmation when users create or resume the changefeed with the
start-ts
orcheckpoint-ts
1 day before the current timestamp #1497
Bug Fixes
ticdc v4.0.12
Improvements
- Add a double confirmation when users create or resume the changefeed with the
start-ts
orcheckpoint-ts
1 day before the current timestamp #1497
Bug Fixes
ticdc v4.0.11
Improvements
- Add the version information in the
capture
metadata and add the CLI version of achangefeed
in thechangefeed
metadata #1342
Bug Fixes
- Fix a bug that the TiCDC service might unexpectedly exit when
ErrTaskStatusNotExists
and the closing ofcapture
session occur at the same time #1240 - Fix the old value switch of a
changefeed
might be affected by anotherchangefeed
#1347 - Fix a bug that the TiCDC service might hang when processing a new
changefeed
with invalid thesort-engine
parameter #1309 - Fix the issue of panic that occurs when getting the debugging information on none owner nodes #1349
- Fix the issue that the
ticdc_processor_num_of_tables
andticdc_processor_table_resolved_ts
metrics are not properly updated when when adding or removing tables #1351 - Fix the issue of potential data loss if a processor crashes when adding a table #1363
- Fix a bug that the owner might lead to abnormal TiCDC server exits during table migrations #1352
- Fix a bug that TiCDC does not exit in time after the service GC safepoint is lost #1367
- Fix a bug that the KV client might skip creating the event feed #1336
- Fix a bug that the atomicity of transactions is broken when the transactions are replicated to the downstream #1375
ticdc v5.0.0-rc
There is no release note for this version.
ticdc v4.0.10
Improvements
- Enable the old value feature if the protocol is
maxwell
#1144 - Enable the unified sorter feature by default #1230
Bug Fixes
- Fix the maxwell issues, including the
base64
data output and output TSO to unix timestamp #1173 - Fix a bug that outdated metadata might cause the newly created changefeed abnormal #1184
- Fix create receiver on closed notifier #1199
- Fix memory accumulated when owner consume etcd update slow #1227
- Fix the issue that
max-batch-size
does not take effect #1253 - Fix cleanup stale tasks before capture information is constructed #1280
- Roll back transactions to recycle db conn for MySQL sink #1285
ticdc v4.0.9
Improvements
- Add an alert for enabling TiKV's Hibernate Region feature #1120
- Reduce memory usage in the schema storage #1127
- Add the feature of unified sorter, which accelerates replication when the data size of the incremental scan is large (experimental) #1122
- Support configuring the maximum message size and the maximum message batch in the TiCDC Open Protocol message (only for Kafka sink) #1079
Bug Fixes
- Fix the issue that multiple owners might exist when the owner campaign key is deleted #1104
- Fix a bug that TiCDC might fail to continue replicating data when a TiKV node crashes or recovers from a crash. This bug only exists in v4.0.8. #1198
- Fix the issue that the metadata is repeatedly flushed to etcd before a table is initialized #1191
- Fix an issue of replication interruption caused by early GC or the latency of updating
TableInfo
when the schema storage caches TiDB tables #1114 - Fix the issue that the schema storage costs too much memory when DDL operations are frequent #1127
- Fix the goroutine leak when a changefeed is paused or stopped #1075
- Increase the maximum retry timeout to 60 seconds in Kafka producer to prevent replication interruption caused by the service or network jitter in the downstream Kafka #1118
- Fix a bug that the Kafka batch size does not take effect #1112
- Fix a bug that some tables' row change might be lost when the network between TiCDC and PD has jitter and when there are paused changefeeds being resumed at the same time #1213
- Fix a bug that the TiCDC process might exit when the network between TiCDC and PD is not stable #1218
- Use a singleton PD client in TiCDC and fix a bug that TiCDC closes PD client by accident which causes replication block #1217
- Fix a bug that the cdc owner might consume too much memory in the etcd watch client
ticdc v4.0.8
ticdc v4.0.7
Improvements
- Support translating more execution-efficient SQL statements in MySQL sink when the old value feature is enabled #955