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

Get DDL owner information form PD by TiDB-API #6961

Closed
zimulala opened this issue Jul 3, 2018 · 4 comments
Closed

Get DDL owner information form PD by TiDB-API #6961

zimulala opened this issue Jul 3, 2018 · 4 comments
Assignees

Comments

@zimulala
Copy link
Contributor

zimulala commented Jul 3, 2018

We want to know easily which TiDB is the DDL owner. Now we can get it from executing SQL. But we only know if the current TiDB is the DDL owner.
So we need to get it from PD. And before that, we need to establish a mapping relationship between the DDL ID and TiDB.

@shenli
Copy link
Member

shenli commented Jul 3, 2018

We could put more information about TiDB in Etcd. Such as ip/name/isOwner/lease/status_port.

@shenli
Copy link
Member

shenli commented Jul 3, 2018

@iamxy PTAL

@zimulala
Copy link
Contributor Author

zimulala commented Jul 3, 2018

I think we needn't the information about "isOwner", we can get it from PD directly after we support the mapping relationship between the DDL ID and TiDB. And if we need "isOwner", we should update it.

@iamxy
Copy link
Member

iamxy commented Jul 3, 2018

At the beginning, this information is enough:

  • listening IP/Port
  • instance's name
  • isOwner
  • some basic configuration such as lease
  • status_port
  • version
  • is binlog opened

@zimulala zimulala changed the title Get DDL owner information form PD by TiDB-ctrl Get DDL owner information form PD by TiDB-API Jul 3, 2018
@zimulala zimulala assigned crazycs520 and unassigned zimulala Jul 3, 2018
@winkyao winkyao closed this as completed Apr 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants