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

tiup playground restart error #992

Closed
fzhedu opened this issue Dec 15, 2020 · 3 comments
Closed

tiup playground restart error #992

fzhedu opened this issue Dec 15, 2020 · 3 comments
Labels
type/bug Categorizes issue as related to a bug.

Comments

@fzhedu
Copy link

fzhedu commented Dec 15, 2020

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

tiup --tag v408 playground
ctrl +c
tiup --tag v408 playground

  1. What did you expect to see?
    normal

  2. What did you see instead?

Start tiflash instance
TiFlash failed to start: error requesting http://127.0.0.1:2379/pd/api/v1/config/replicate, response: "cannot disable placement rules with TiFlash nodes"
, code 500

mac:tiflash-0 fzh$ tiup --tag v408 playground display
Starting component playground: /Users/fzh/.tiup/components/playground/v1.2.5/tiup-playground display
Error: Post http://127.0.0.1:9527/command: EOF
Error: run /Users/fzh/.tiup/components/playground/v1.2.5/tiup-playground (wd:/Users/fzh/.tiup/data/v408) failed: exit status 1
4. What version of TiUP are you using (tiup --version)?
1.2.5

@fzhedu fzhedu added the type/bug Categorizes issue as related to a bug. label Dec 15, 2020
@lucklove
Copy link
Member

lucklove commented Dec 15, 2020

Root cause: https://github.com/pingcap/tiup/blob/master/components/playground/instance/tiflash.go#L126

The playground will try to set EnablePlacementRules as false to update MaxReplicas if there is tiflash node. However, it seems PD will refuse to this action if there is tiflash node. So the result is that we can start the playground the first time (because pd don't know there is a tiflash yet), but not the second time.

So maybe for the second time, we should skip UpdateReplicateConfig

@JaySon-Huang
Copy link
Contributor

Or we can use this API to update the replica number when the placement-rules is enabled.

https://asktug.com/t/topic/36677/8

@AstroProfundis
Copy link
Contributor

This is already fixed in #1280

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Categorizes issue as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants