lightning: fix lightning failed to log encoding error (#45241)

[ti-chi-bot]

This is an automated cherry-pick of #45241

What problem does this PR solve?

Issue Number: close #44321

Problem Summary:

When the source file has ill-formated row, the row is very large so it can't be logged. We can't locate the bad row;

2023-06-01 10:55:27.887067902 +0800 CST m=+35.508861459 write error: write length 20297970322 exceeds maximum file size 536870912

What is changed and how it works?

When we encounter ill-formatted row, we take out the ill-formatted row and only log the first 1024 characters of the row, so that it would not report error that write length exceeds maximum file size.

Before fixing the issue, the log looks like this when encountering ill-formatted row:

[2023/07/06 22:23:38.812 +08:00] [INFO] [base_test.go:40] ["logger is initialized"]
2023-07-06 22:23:39.344279 +0800 CST m=+0.575101501 write error: write length 1050272 exceeds maximum file size 1048576
2023-07-06 22:23:39.353842 +0800 CST m=+0.584668709 write error: write length 1050249 exceeds maximum file size 1048576

The length of the row is 324.

After fixing the issue, the log looks like this when encountering ill-formatted row:

[2023/07/07 21:08:03.211 +08:00] [INFO] [base_test.go:41] ["logger is initialized"]
[2023/07/07 21:08:03.737 +08:00] [ERROR] [base.go:308] ["kv convert failed"] [original=test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test] [originalCol=6] [colName=c1] [colType=tinyint(4)] []
[2023/07/07 21:08:03.737 +08:00] [ERROR] [base.go:315] ["failed to convert kv value"] [origVal=test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test_test] [fieldType=tinyint(4)] [column=c1] [columnID=7]

The length of the row is 2419.

So to check whether the "exceeds maximum file size" issue has been fixed, we could check whether the length of the row is larger than 500, which can make sure the log shows the first 1024 characters of the ill-formatted row instead of saying "write error: write length xxx exceeds maximum file size xxx".

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

When lightning encounters ill-formatted row, it can log the encoding error within which shows the first 1024 characters of the row content, instead of logging the write error that write length exceeds maximum file size.

[lyzx2001]

/cherry-pick-invite

[ti-chi-bot]

@lyzx2001 Please accept the invitation then you can push to the cherry-pick pull requests.
Comment with "/cherry-pick-invite" if the invitation is expired.
https://github.com/ti-chi-bot/tidb/invitations

[lyzx2001]

/cc @lance6716

[lyzx2001]

/cc @D3Hunter

[D3Hunter]

/lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [D3Hunter,lance6716]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-07-20 07:01:50.84281693 +0000 UTC m=+1179402.613155643: ☑️ agreed by lance6716.
• 2023-07-24 05:47:06.874443508 +0000 UTC m=+160569.468974498: ☑️ agreed by D3Hunter.