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

When the delete sql exceeds 256MB, the 4000th port of tidb node stops. #7861

Closed
httpcheck opened this issue Oct 10, 2018 · 6 comments
Closed
Labels
type/question The issue belongs to a question.

Comments

@httpcheck
Copy link

As the title says,when the delete sql exceeds 256MB, the 4000th port of tidb node stops.
What I want to know is how to write the sql when I want to delete the information of the large table.

@httpcheck httpcheck reopened this Oct 10, 2018
@eurekaka eurekaka added the type/question The issue belongs to a question. label Oct 10, 2018
@jackysp
Copy link
Member

jackysp commented Oct 10, 2018

Thanks for your report, @bianxindong !
Do you mean the size of the SQL file is larger than 256MB?
Please provide the TiDB server's log and TiDB version.

@httpcheck
Copy link
Author

Thanks for your report, @bianxindong !
Do you mean the size of the SQL file is larger than 256MB?
Please provide the TiDB server's log and TiDB version.

image
image
image
image
image

tidb version :
Release Version: v2.0.1
Git Commit Hash: 389703a
Git Commit Branch: release-2.0
UTC Build Time: 2018-05-16 03:39:30
GoVersion: go version go1.10.2 linux/amd64
TiKV Min Version: 2.0.0-rc.4.1

When rd exec the delete sql,our alarm system called me the result. All 4000th ports of tidb nodes were down.I had to exec the script of stop_tidb.sh and start_tidb.sh,and then those service were back to normal.

@jackysp
Copy link
Member

jackysp commented Oct 10, 2018

It seems a fixed issue. Could you please update to the latest version v2.0.7?
I'll ask an expert for help.
PTAL @WangXiangUSTC .

@WangXiangUSTC
Copy link
Contributor

seems fixed in this pr #7086
you can update to v2.0.7 and try again. @bianxindong

@httpcheck
Copy link
Author

When our service is back to normal, I exec the sql that's added condition. It looks ok.
So the limitation of memory is 256MB, Did what I operated cause out of memory ?

@zhexuany
Copy link
Contributor

@bianxindong It is a fixed problem. You did not do anything wrong. Rather, it is a problem on our side. Closing since the problem had been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question The issue belongs to a question.
Projects
None yet
Development

No branches or pull requests

5 participants