error message "connect: cannot assign requested address" on AUTO_ID_CACHE=1 tables #48869
Labels
affects-6.4
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-6.6
affects-7.0
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.2
affects-7.3
affects-7.4
affects-7.5
This bug affects the 7.5.x(LTS) versions.
fixes-6.5.6
fixes-7.1.3
fixes-7.5.1
report/customer
Customers have encountered this bug.
severity/major
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
A user is using DM to migrate to TiDB, and they have lots of tables with AUTO_ID_CACHE=1.
During the migration, some errors occured.
The error message looks like this:
This error message indicate that the tcp ports are used up... the root cause is grpc client leak.\
There are two ways for the leak:
1. Minimal reproduce step (Required)
Check the TCP connection counts before:
The execute the following SQLs:
Check the tcp connections after that:
2. What did you expect to see? (Required)
create table with AUTO_ID_CACHE=1 should not increase the tcp connection of tidb
3. What did you see instead (Required)
Each table with AUTO_ID_CACHE=1 would increase the tcp connection of tidb
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: