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.

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

releases: add tidb 5.0.4 release notes #7112

Merged
merged 11 commits into from
Sep 27, 2021
Merged

Conversation

TomShawn
Copy link
Contributor

@TomShawn TomShawn commented Sep 10, 2021

What is changed, added or deleted? (Required)

releases: add tidb 5.0.4 release notes

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

  • master (the latest development version)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Sep 10, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • Liuxiaozhen12

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added missing-translation-status This PR does not have translation status info. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 10, 2021
@TomShawn TomShawn added needs-cherry-pick-release-5.0 translation/from-docs This PR is translated from a PR in pingcap/docs. and removed missing-translation-status This PR does not have translation status info. labels Sep 10, 2021

## 提升改进

## Bug 修复
Copy link
Contributor

@Little-Wallace Little-Wallace Sep 14, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Tools

    + Dumpling
             - 修复对 mysql-8.0.3 或更高版本执行 `show table status` 卡住的问题。
             - 支持 MemSQL/SingleStore 的 `WITH CONSISTENT SNAPSHOT` 和 `SHOW CREATE DATABASE` 语法。
       
     + TiCDC
    
             - 修复将 `mysql.TypeString, mysql.TypeVarString, mysql.TypeVarchar` 等类型的数据编码为 json 时进程崩溃的 Bug。 [#2782](https://github.com/pingcap/ticdc/pull/2782)
             - 修复表重新调度时多个流写同一张表引发的数据不一致 Bug。 [#2728](https://github.com/pingcap/ticdc/pull/2728)
             - 降低 gRPC 窗口大小来避免 Region 数量过多时触发 OOM。  [#2724](https://github.com/pingcap/ticdc/pull/2724)
             - 修复内存压力大时 gRPC 连接频繁断开的错误。 [#2719](https://github.com/pingcap/ticdc/pull/2719)
             - 优化内存排序后端的内存回收效率。 [#2711](https://github.com/pingcap/ticdc/pull/2711)
             - 修复无符号整数的类型转换错误。 [#2655](https://github.com/pingcap/ticdc/pull/2655)
             - 修复 open protocol 在上游事务插入并删除同一行数据情况下输出空值的问题. [#2620](https://github.com/pingcap/ticdc/pull/2620)
             - 修复表结构变更时创建的流处理 DDL 失败的问题。 [#2610](https://github.com/pingcap/ticdc/pull/2610)
             - 修复执行缓慢的 DDL 阻塞其他流复制数据的问题。[#2605](https://github.com/pingcap/ticdc/pull/2605)
             - 禁止使用不同的版本启动 TiCDC 节点。 [#2598](https://github.com/pingcap/ticdc/pull/2598)
             - 修复元信息管理问题。 [#2558](https://github.com/pingcap/ticdc/pull/2558)
             - 为所有 KV 客户端创建全局共享的 gRPC 连接池。 [#2533](https://github.com/pingcap/ticdc/pull/2533)
             - 修复 sink Close 不正确导致多个节点写同一张表的 Bug。 [#2492](https://github.com/pingcap/ticdc/pull/2492)
             - 降低了 workerpool 中创建 goroutine 的数量. [#2487](https://github.com/pingcap/ticdc/pull/2487)
             - 修复 capture list 命令中出现已经关闭的 capture 的 Bug。 [#2466](https://github.com/pingcap/ticdc/pull/2466)
             - 修复集成测试中遇到的由于 DDL Job 重复导致的 ErrSchemaStorageTableMiss 错误. [#2458](https://github.com/pingcap/ticdc/pull/2458)
             - 修复遇到 ErrGCTTLExceeded 错误时 changefeed 无法删除的 Bug。 [#2456](https://github.com/pingcap/ticdc/pull/2456)
             - 修复同步大数据量表到 cdclog 失败的 Bug。 [#2445](https://github.com/pingcap/ticdc/pull/2445)
             - 修复客户端向后兼容。 [#2413](https://github.com/pingcap/ticdc/pull/2413)
             - 修复 Region 从某个 TiKV 节点全部迁移走时,回收其对应的 CDC worker 的 goroutine 资源 [#2377](https://github.com/pingcap/ticdc/pull/2377)
             - 删除已经不再维护的 FileSorter 代码。 [#2326](https://github.com/pingcap/ticdc/pull/2326)
             - 默认从 TiKV 获取行变更的历史值(old-value),输出会根据 enable-old-value 配置进行调整。 [#2305](https://github.com/pingcap/ticdc/pull/2305)
             - 修复 SinkManager 中对 map 的不安全并发访问。 [#2299](https://github.com/pingcap/ticdc/pull/2299)
             - 修复 owner 在执行 DDL 时崩溃可能导致的潜在的 DDL 任务丢失的 Bug。[#2292](https://github.com/pingcap/ticdc/pull/2292)
            - 修复在 region 刚初始化时立刻执行 resolve lock 的问题。 [#2265](https://github.com/pingcap/ticdc/pull/2265)
            - 修复创建新的分区表时部分分区被重复分发。 [#2263](https://github.com/pingcap/ticdc/pull/2263)
           - 优化 PD 缺失证书时的报错信息。 [#2185](https://github.com/pingcap/ticdc/pull/2185)
           - 当任务结束时清除 changefeed 和 processor 的监控指标。 [#2177](https://github.com/pingcap/ticdc/pull/2177)
    

Copy link
Contributor

@amyangfei amyangfei Sep 14, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/即便用户没有配置,仍然上传 old-value 到 CDC 节点。/ 默认从 TiKV 获取行变更的历史值(old-value),输出会根据 enable-old-value 配置进行调整

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • 修复当一张表的状态从不合法变更为合法时,数据没有被 CDC 复制的 Bug。 #1488

这个没合并,需要去掉

releases/release-5.0.4.md Show resolved Hide resolved
releases/release-5.0.4.md Show resolved Hide resolved
@ti-chi-bot ti-chi-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 15, 2021
releases/release-5.0.4.md Show resolved Hide resolved
releases/release-5.0.4.md Show resolved Hide resolved
releases/release-5.0.4.md Show resolved Hide resolved
releases/release-5.0.4.md Show resolved Hide resolved
@ti-chi-bot ti-chi-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Sep 17, 2021

+ TiKV

?- 修复当有快照文件未被 GC 回收时,快照在 GC 的过程中可能遗留 GC 快照文件的问题 [#10813](https://github.com/tikv/tikv/issues/10813)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- 修复损坏的快照文件可能会造成磁盘空间无法回收的问题。[#10813](https://github.com/tikv/tikv/issues/10813)

Copy link
Contributor

@djshow832 djshow832 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot
Copy link
Member

@djshow832: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

In response to this:

LGTM

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@tier-cap
Copy link
Contributor

LGTM for TiKV

@Little-Wallace
Copy link
Contributor

LGTM for tools

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Sep 27, 2021
@TomShawn
Copy link
Contributor Author

/remove-status LGT1
/status LGT2

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Sep 27, 2021
@TomShawn
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 21323cb

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Sep 27, 2021
@ti-chi-bot ti-chi-bot merged commit ed8ea62 into pingcap:master Sep 27, 2021
@TomShawn TomShawn deleted the 5.0.4-rn branch September 27, 2021 03:27
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #7194.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #7195.

@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #7196.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/L Denotes a PR that changes 100-499 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. translation/from-docs This PR is translated from a PR in pingcap/docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants