pingcap / pingcap/tiup

cluster: wrong ngm config

Open
#2,170 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/bug
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
  1. What did you expect to see?

right pd address in config file like ["127.0.0.1:2379", "127.0.0.1:2339"]

  1. What did you see instead?

wrong pd address in config file like ["127.0.0.1:2379" "127.0.0.1:2339"]

  1. What version of TiUP are you using (tiup --version)?
    v1.12.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a source file or test. Reproduce the cluster configuration problem with TiUP v1.12.0 and trace where the PD address list is generated or serialized. Done means the config contains a valid comma-separated list such as ["127.0.0.1:2379", "127.0.0.1:2339"] rather than adjacent quoted values.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.