This repository was archived by the owner on Jul 26, 2025. It is now read-only.
Open
Conversation
889d255 to
be0f0ce
Compare
|
Any reason why this is not merged? |
|
+1. this will be extremely useful for me to eval tiflash. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: You may need to provide enough resources for docker. For example, 8 CPUs and 10GB memory.
Here is the instruction to test:
Start the services:
$docker-compose -f docker-compose-tiflash-nightly.yml pull$docker-compose -f docker-compose-tiflash-nightly.yml up -dConnect to TiDB (you may need to wait a minute or so to wait for everything to start)
$mysql -h 127.0.0.1 -P 4000 -u rootTest TiFlash
To stop services:
$docker-compose -f docker-compose-tiflash-nightly.yml stop