ddl: Fix snap after dropping database

[JaySon-Huang]

What problem does this PR solve?

Issue Number: close #8506

Problem Summary:

Introduced by #8536. In that PR, we don't check whether the DatabaseInfo exist when creating a Storage instance.

However, if the DDL "create database" and decoding raftlog or snapshot comes after TiDB executed "drop database". Then applyCreateStorageInstance can not handle it because the IDatabase instance is not created in TiFlash.

What is changed and how it works?

In order to resolve the DatabaseInfo can not be fetched from TiKV, we will construct a "fake" DatabaseInfo and create the IDatabase instance in TiFlash. Because

• If the database is not FLASHBACK, then we don't care its display name in TiFlash, we just need it for storing the raft log / snapshot data
• If the database is FLASHBACK later, then the DatabaseInfo will be overwritten

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

None

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-all-tests

[hongyunyan]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongyunyan, Lloyd-Pottiger

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 [Lloyd-Pottiger,hongyunyan]

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-12-21 08:11:02.173747579 +0000 UTC m=+1121353.210974505: ☑️ agreed by Lloyd-Pottiger.
• 2023-12-22 06:23:50.942701608 +0000 UTC m=+1201321.979928535: ☑️ agreed by hongyunyan.

[JaySon-Huang]

/run-all-tests

[Lloyd-Pottiger]

/run-integration-test

[JaySon-Huang]

https://ci.pingcap.net/blue/organizations/jenkins/tiflash-ghpr-integration-tests/detail/tiflash-ghpr-integration-tests/15571/pipeline

[2023-12-22T07:45:35.409Z] fullstack-test/mpp/async_server_alarm.test: Running
[2023-12-22T07:46:24.648Z]   File: fullstack-test/mpp/async_server_alarm.test
[2023-12-22T07:46:24.648Z]   Error line: 58
[2023-12-22T07:46:24.648Z]   Error: use test; set @@tidb_isolation_read_engines='tiflash'; set @@tidb_allow_mpp=1; select count(value), id from t group by id;
[2023-12-22T07:46:24.648Z]   Result:
[2023-12-22T07:46:24.648Z]     ERROR 1105 (HY000) at line 1: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout
[2023-12-22T07:46:24.648Z]   Expected:
[2023-12-22T07:46:24.648Z]     {#REGEXP}.*Can't find task*

[JaySon-Huang]

/run-integration-test

[JaySon-Huang]

/run-integration-test

[ti-chi-bot]

@JaySon-Huang: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #8572.