pingcap / docs-cn Goto Github PK

View Code? Open in Web Editor NEW

1.8K 207.0 1.2K 267.28 MB

TiDB/TiKV/PD 中文文档

Home Page: https://docs.pingcap.com/zh

License: Other

Shell 38.36% Python 26.82% TeX 32.20% Smarty 2.61%

tidb-documentation hacktoberfest tidb

docs-cn's Issues

backoffer.maxSleep

日志提示：“Error Code: 1105. [try again later]: backoffer.maxSleep 15000ms is exceeded, errors: stale_epoch:<> not leader: region_id:4204 , ctx: region_id:4204 region_epoch:<conf_ver:5 version:183 > peer:<id:4207 store_id:5 > stale_epoch:<> ”
请问是否需要配置这个maxsleep。如何配置呢？

pd-server:不断报告warning，clock offset

"2017/04/10 11:10:03 tso.go:122: [warning] clock offset: 205.626449ms, prev: 2017-04-10 11:10:02.820721481 +0800 HKT, now: 2017-04-10 11:10:03.02634793 +0800 HKT"
请问，该问题是否严重，可能是什么导致的呢？

一般我们用mysql会做只读的实例，tidb在处理一条耗时很长的sql时，会影响插入和读取请求吗？

RT。

insert and load data performance

目前TiDB执行insert或是load command 的执行效能有相关的数据可供参考吗？
就自己本身的测试insert速度都不到100K/秒（测试环境为4台server架cluster）,而我们产品的预期insert至少要能达到150K/sec.

varchar字段长度与mysql不匹配

我用的是最新的版本，搭建的是单机版的测试环境，发现字符串的长度与mysql不匹配，比如我定义的字段为varchar（10），经过测试实际只能存放4个字符，请问怎么解决？

./loader command parameter error

This command has no -q parameters

tidb是否有面向查询的缓存！

类似mysql的pool-cache，read-cache？

Add a document for adding/removing/migrating tikv instance.

We need a document about how to add new tikv instance to a cluster, how to remove a tikv instance from a cluster and how to move a tikv instance from one machine to another machine.

loader导入数据出错

由于历史原因，我们有个数据库名字是order.使用loader工具导入数据库时会产生语句use order;由于order是mysql的关键字，这里就会报错。

README.md - click PingCAP techblog link returns 404

When click 'PingCAP团队技术博客' in README.md, it just returns below 404 page:

Submitted PR #139 to fix this.

Add document for privileges

使用 Ansible 部署集群时，在 start 阶段的 wait up 时长时间卡死

卡死一段时间后提示：

fatal: [xx.xx.xx.xx]: FAILED! => {"changed": false, "elapsed": 300, "failed": true, "msg": "Timeout when waiting for search string 200 OK in xx.xx.xx.xx:9100"}
fatal: [xx.xx.xx.xx]: FAILED! => {"changed": false, "elapsed": 300, "failed": true, "msg": "Timeout when waiting for search string 200 OK in xx.xx.xx.xx:9100"}
fatal: [xx.xx.xx.xx]: FAILED! => {"changed": false, "elapsed": 300, "failed": true, "msg": "Timeout when waiting for search string 200 OK in xx.xx.xx.xx:9100"}
fatal: [xx.xx.xx.xx]: FAILED! => {"changed": false, "elapsed": 300, "failed": true, "msg": "Timeout when waiting for search string 200 OK in xx.xx.xx.xx:9100"}
fatal: [xx.xx.xx.xx]: FAILED! => {"changed": false, "elapsed": 300, "failed": true, "msg": "Timeout when waiting for search string 200 OK in xx.xx.xx.xx:9100"}

然后继续卡死

系统环境：Ubuntu 16.04

tidb-server:执行mydumper导入数据过程中进程退出！

使用mydumper导入数据，执行大约3小时后，tidb-server异常退出！
日志信息最后一段如下：
“accept error accept tcp [::]:4000: accept4: too many open files�[0m”
在该信息前出现大量如下错误信息：
“2017/04/07 09:28:06 client.go:227: �[0;31m[error] [pd] failed updateLeader: failed to get leader from [http://192.168.20.157:2379 http://192.168.20.158:2379 http://192.168.20.160:2379]�[0m
2017/04/07 09:28:09 client.go:227: �[0;31m[error] [pd] failed updateLeader: failed to get leader from [http://192.168.20.157:2379 http://192.168.20.158:2379 http://192.168.20.160:2379]�[0m
”
请问各位，accept error accept tcp的错误是不是因为前述连接失效但是连接没有释放导致？
还有什么可能的原因吗？我们需要做什么？谢谢！

navicat (windows) can't show databases list with tidb

用navicat客户端链接后显示不了数据库

数据库检查无报错，但导入报错

2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_task_sub 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_task_sub succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_task_tpl 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_task_tpl succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_tools 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_tools succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_tools_unit 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_tools_unit succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_tools_user 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_tools_user succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_topics 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_topics succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_topics_resource 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_topics_resource succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_web_config 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_web_config succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_withdraw 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_withdraw succ 2017/07/12 17:15:49 checker.go:63: [info] Checking table aipu_withdraw_lock 2017/07/12 17:15:49 checker.go:69: [info] Check table aipu_withdraw_lock succ Check database succ!
检查的时候都是可以的没有报错，但是导入的时候就有很多报错了

2017/07/12 17:17:37 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_member_auth-schema.sql[finished] 2017/07/12 17:17:38 db.go:117: [warning] sql execution costs 1.397327 seconds, UPDATE tidb_loader.checkpoint SET offset=1000056 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:38 db.go:117: [warning] sql execution costs 1.397623 seconds, UPDATE tidb_loader.checkpoint SET offset=1000056 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:38 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_product-schema.sql[finished] 2017/07/12 17:17:38 loader.go:135: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_product.sql[start] 2017/07/12 17:17:39 loader.go:193: [info] data file ../sql/zjcool_system.aipu_product.sql scanned finished. 2017/07/12 17:17:39 loader.go:144: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_product.sql[finished] 2017/07/12 17:17:39 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_talk-schema.sql[finished] 2017/07/12 17:17:40 db.go:117: [warning] sql execution costs 1.698652 seconds, UPDATE tidb_loader.checkpoint SET offset=2000024 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:40 db.go:117: [warning] sql execution costs 1.698946 seconds, UPDATE tidb_loader.checkpoint SET offset=2000024 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:40 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_web_config-schema.sql[finished] 2017/07/12 17:17:40 loader.go:135: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_web_config.sql[start] 2017/07/12 17:17:40 loader.go:193: [info] data file ../sql/zjcool_system.aipu_web_config.sql scanned finished. 2017/07/12 17:17:40 loader.go:144: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_web_config.sql[finished] 2017/07/12 17:17:41 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_withdraw-schema.sql[finished] 2017/07/12 17:17:41 loader.go:135: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_withdraw.sql[start] 2017/07/12 17:17:41 db.go:117: [warning] sql execution costs 1.421965 seconds, UPDATE tidb_loader.checkpoint SET offset=5999709 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:41 db.go:117: [warning] sql execution costs 1.828666 seconds, UPDATE tidb_loader.checkpoint SET offset=5999709 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:41 db.go:117: [warning] sql execution costs 1.828870 seconds, UPDATE tidb_loader.checkpoint SET offset=5999709 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:41 loader.go:193: [info] data file ../sql/zjcool_system.aipu_withdraw.sql scanned finished. 2017/07/12 17:17:41 db.go:117: [warning] sql execution costs 1.152012 seconds, UPDATE tidb_loader.checkpoint SET offset=2999996 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:41 db.go:117: [warning] sql execution costs 1.152330 seconds, UPDATE tidb_loader.checkpoint SET offset=2999996 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:42 db.go:117: [warning] sql execution costs 1.002204 seconds, UPDATE tidb_loader.checkpoint SET offset=6999654 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:42 db.go:117: [warning] sql execution costs 1.003306 seconds, UPDATE tidb_loader.checkpoint SET offset=6999654 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:42 loader.go:144: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_task_request.sql[finished] 2017/07/12 17:17:42 db.go:117: [warning] sql execution costs 1.435143 seconds, CREATE TABLE aipu_bill_sum (id int(11) NOT NULL AUTO_INCREMENT,uidint(11) NOT NULL DEFAULT '0 2017/07/12 17:17:42 db.go:117: [warning] sql execution costs 1.436374 seconds, CREATE TABLEaipu_bill_sum (id int(11) NOT NULL AUTO_INCREMENT,uidint(11) NOT NULL DEFAULT '0 2017/07/12 17:17:42 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_bill_sum-schema.sql[finished] 2017/07/12 17:17:42 loader.go:135: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_bill_sum.sql[start] 2017/07/12 17:17:42 loader.go:193: [info] data file ../sql/zjcool_system.aipu_bill_sum.sql scanned finished. 2017/07/12 17:17:42 db.go:117: [warning] sql execution costs 1.476377 seconds, UPDATE tidb_loader.checkpoint SET offset=1000067 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:42 db.go:117: [warning] sql execution costs 1.489026 seconds, UPDATE tidb_loader.checkpoint SET offset=1000067 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:43 db.go:117: [warning] sql execution costs 1.771141 seconds, UPDATE tidb_loader.checkpoint SET offset=3999928 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:43 db.go:117: [warning] sql execution costs 1.771358 seconds, UPDATE tidb_loader.checkpoint SET offset=3999928 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:44 db.go:117: [warning] sql execution costs 1.702975 seconds, CREATE TABLEaipu_task_config (id int(11) NOT NULL AUTO_INCREMENT,keyvarchar(200) NOT NULL CO 2017/07/12 17:17:44 db.go:117: [warning] sql execution costs 1.705090 seconds, CREATE TABLEaipu_task_config (id int(11) NOT NULL AUTO_INCREMENT,keyvarchar(200) NOT NULL CO 2017/07/12 17:17:44 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_task_config-schema.sql[finished] 2017/07/12 17:17:44 loader.go:135: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_task_config.sql[start] 2017/07/12 17:17:44 loader.go:193: [info] data file ../sql/zjcool_system.aipu_task_config.sql scanned finished. 2017/07/12 17:17:44 db.go:117: [warning] sql execution costs 2.071975 seconds, UPDATE tidb_loader.checkpoint SET offset=1999889 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:44 db.go:117: [warning] sql execution costs 2.072213 seconds, UPDATE tidb_loader.checkpoint SET offset=1999889 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu 2017/07/12 17:17:44 loader.go:635: [info] [loader][run table schema]../sql/zjcool_system.aipu_task_seller-schema.sql[finished] 2017/07/12 17:17:44 db.go:117: [warning] sql execution costs 2.365653 seconds, UPDATE tidb_loader.checkpoint SET offset=357827 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu_ 2017/07/12 17:17:44 db.go:117: [warning] sql execution costs 2.366338 seconds, UPDATE tidb_loader.checkpoint SET offset=357827 WHERE id ='2b5d4c' AND filename='zjcool_system.aipu_ 2017/07/12 17:17:44 loader.go:144: [info] [loader][restore table data sql]../sql/zjcool_system.aipu_bill_sum.sql[finished]

动态加pd,name值为空，无法对此PD进行操作

{
"members": [
{
"name": "",
"peer_urls": [
"http://172.16.16.122:2380"
]
},
{
"name": "pd1",
"client_urls": [
"http://172.16.16.115:2379"
],
"peer_urls": [
"http://172.16.16.115:2380"
]
},
{
"name": "pd3",
"client_urls": [
"http://172.16.16.117:2379"
],
"peer_urls": [
"http://172.16.16.117:2380"
]
}
]
}

建议弄个版本号

建议使用release版本号，1.0 或者1.0.0 再或者0.0.1，不为别的，约定俗成。

能否加个像oracle的序列一样的功能

权限管理问题

tidb的grant授权时不支持ip地址'ops'@'192.168.19.0/255.255.255.0'这种写法，这样配置完后会一直显示主机连接被拒绝

create user 'ops'@'192.168.19.0/255.255.255.0' identified by 'opstest';

请问如何安全地重启或关闭各个服务？

包括db/pd/kv server。

fatal error: concurrent map read and map write

tidb-server 报错退出。日志请参见附件。
幸好部署两个tidb-server。前端有lvs所以没有发生使用问题。但还是想了解是为什么？
tidblog02.txt

pd server报错

2016/12/29 17:04:09 tso.go:155: [error] we haven't synced timestamp ok, wait and retry, retry count 99
2016/12/29 17:04:09 conn.go:102: [error] handle request header:<uuid:"\364\276E\355\034j@\320\225\307\221g\007"\350u" cluster_id:6369440677371556373 > cmd_type:Tso tso:<count:1 > err /home/jenkins/workspace/BUILD_PD_WORKFLOW/go/src/github.com/pingcap/pd/server/tso.go:169: can not get timestamp
/home/jenkins/workspace/BUILD_PD_WORKFLOW/go/src/github.com/pingcap/pd/server/command.go:33:
2016/12/29 17:04:09 conn.go:75: [error] read request message err EOF

该服务器时钟服务是正常的，与集群里其他机器也是同步的，这个错误是怎么导致的？该如何解决？

create 语句里的bit(m)类型默认值不支持b'1'值

报invalid default value for xxx 错误

FAQ needed.

for user's convenience and fast problem tracking, we need to provide FAQ in Chinese.

add doc for load/import data

Is it ok to set sync-log = false for production use?

If I set sync-log to false, in which case it will cause data loss?
Server crash? Operating System crash?

TODO: describe common error logs in trouble-shooting

trouble-shooting.md should contain common error logs and corresponding solutions.

rc2:升级安装后，pd-ctl无法运行

下载最新的rc2版本安装后，所有功能运行正常，但是使用pd-ctl查询状态等信息，pd-ctl返回错误。具体信息：
① pd-server client端口2379
② 检查端口可用（使用webapi访问能获取信息）
③ 使用pd-ctl查询失败，具体命令输入如下：
pd-ctl -u 192.168.20.157:2379

member
返回错误：“parse 192.168.20.157:2379: first path segment in URL cannot contain colon”
Any suggestion ？

Is there any quick start guide in Chinese?

I found that a quick start guide is extremely helpful. In fact, my most visited page in pingcap/docs is the Quick Start Guide.

docker环境里，如何在一台机器部署TiDB

TiDB Docker 部署方案写的应该是用了6台docker宿主机部署TiDB，这其实没有完全发挥docker的优越性。如何在一台docker宿主机理部署TiDB集群

run table schema failed - driver: bad connection

loader导入数据遇到这个问题，请问什么原因导致的？

2017/07/03 01:54:29 loader.go:674: [fatal] run table schema failed - driver: bad connection
/home/jenkins/workspace/build_tidb_enterprise_tools_master/go/src/github.com/pingcap/tidb-enterprise-tools/loader/db.go:84:
/home/jenkins/workspace/build_tidb_enterprise_tools_master/go/src/github.com/pingcap/tidb-enterprise-tools/loader/loader.go:558:

Add a new section in FAQ to describe auto-rebalance

为什么checker都报错，这些最基本的表为什么不支持？

数据迁移前线使用了checker，但发现每个表都报错了
后拿了文档范例的表也一样
为什么会这样？

# ./checker -host 127.0.0.1 -port 23307 -user root -password ??????? test t1

2017/06/06 17:46:12 checker.go:48: [info] Checking database test
2017/06/06 17:46:12 main.go:39: [info] Database DSN: root:??????@tcp(127.0.0.1:23307)/test?charset=utf8
2017/06/06 17:46:12 checker.go:63: [info] Checking table t1
2017/06/06 17:46:12 checker.go:67: [error] Check table t1 failed with err: line 0 column 18 near "(
  "id" int(11) NOT NULL DEFAULT '0',
  "age" int(11) DEFAULT NULL,
  PRIMARY KEY ("id")
) ENGINE=InnoDB DEFAULT CHARSET=utf8" (total length 144)
github.com/pingcap/tidb/parser/yy_parser.go:96: 
github.com/pingcap/tidb/parser/yy_parser.go:109: 
/home/jenkins/workspace/build_tidb_tools_master/go/src/github.com/pingcap/tidb-tools/checker/checker.go:122:  parse CREATE TABLE "t1" (
  "id" int(11) NOT NULL DEFAULT '0',
  "age" int(11) DEFAULT NULL,
  PRIMARY KEY ("id")
) ENGINE=InnoDB DEFAULT CHARSET=utf8 error
/home/jenkins/workspace/build_tidb_tools_master/go/src/github.com/pingcap/tidb-tools/checker/checker.go:114: 
2017/06/06 17:46:12 main.go:83: [error] Check database test with 1 errors and 0 warnings

连续插入数据报Information schema is out of date

我在从Hbase把数据导入到tidb的时候，批量插入一阵子就会报这个错误，请问这个错误是因为我客户端申请的连接太多还是什么导致的，重新启动插入又会好一会儿再报这个错误。

2017/02/22 12:39:04 2pc.go:129: [info] [BIG_TXN] table id:144 size:4202137, keys:60000, puts:60000, dels:0, locks:0, startTS:390001680197877761
2017/02/22 12:39:04 2pc.go:129: [info] [BIG_TXN] table id:144 size:4487166, keys:60000, puts:60000, dels:0, locks:0, startTS:390001680184770563
2017/02/22 12:39:07 2pc.go:129: [info] [BIG_TXN] table id:144 size:4204384, keys:60000, puts:60000, dels:0, locks:0, startTS:390001681062952961
2017/02/22 12:39:08 2pc.go:129: [info] [BIG_TXN] table id:144 size:4191993, keys:60000, puts:60000, dels:0, locks:0, startTS:390001681233346562
2017/02/22 12:39:09 session.go:230: [warning] [0] finished txn:<nil>, [domain:1]Information schema is out of date.
2017/02/22 12:39:09 session.go:466: [warning] [0] session error:
[domain:1]Information schema is out of date.
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/store/tikv/2pc.go:532: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/store/tikv/2pc.go:504: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/store/tikv/txn.go:152: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/session.go:208: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/session.go:231: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/tidb.go:186: 
{
  "currDBName": "",
  "id": 0,
  "stauts": 2,
  "strictMode": true,
  "user": ""
}
2017/02/22 12:39:09 session.go:466: [warning] [0] session error:
[domain:1]Information schema is out of date.
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/store/tikv/2pc.go:532: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/store/tikv/2pc.go:504: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/store/tikv/txn.go:152: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/session.go:208: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/session.go:231: 
/home/jenkins/workspace/TIDB_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb/tidb.go:186: 
{
  "currDBName": "",
  "id": 0,
  "stauts": 2,
  "strictMode": true,
  "user": ""
}
2017/02/22 12:39:09 gc_worker.go:115: [warning] [gc worker] check leader err: [domain:1]Information schema is out of date.
2017/02/22 12:39:09 2pc.go:478: [info] 2PC clean up done, tid: 390001680669736962
2017/02/22 12:39:10 2pc.go:129: [info] [BIG_TXN] table id:144 size:4241279, keys:60000, puts:60000, dels:0, locks:0, startTS:390001681547919362
2017/02/22 12:39:10 2pc.go:129: [info] [BIG_TXN] table id:144 size:4272906, keys:60000, puts:60000, dels:0, locks:0, startTS:390001681665884161
2017/02/22 12:39:11 2pc.go:129: [info] [BIG_TXN] table id:144 size:4199064, keys:60000, puts:60000, dels:0, locks:0, startTS:390001681862492162
2017/02/22 12:39:13 2pc.go:129: [info] [BIG_TXN] table id:144 size:4199854, keys:60000, puts:60000, dels:0, locks:0, startTS:390001682517852162
2017/02/22 12:39:15 2pc.go:129: [info] [BIG_TXN] table id:144 size:4201273, keys:60000, puts:60000, dels:0, locks:0, startTS:390001683015925762
2017/02/22 12:39:15 2pc.go:129: [info] [BIG_TXN] table id:144 size:4204160, keys:60000, puts:60000, dels:0, locks:0, startTS:390001683199426561
2017/02/22 12:39:16 server.go:192: [info] [320] close connection
2017/02/22 12:39:16 server.go:192: [info] [374] close connection
2017/02/22 12:39:16 server.go:192: [info] [317] close connection
2017/02/22 12:39:16 server.go:192: [info] [321] close connection
2017/02/22 12:39:16 server.go:192: [info] [322] close connection
2017/02/22 12:39:16 server.go:192: [info] [322] close connection
2017/02/22 12:39:16 server.go:192: [info] [312] close connection
2017/02/22 12:39:16 server.go:192: [info] [309] close connection
2017/02/22 12:39:16 server.go:192: [info] [310] close connection
2017/02/22 12:39:16 server.go:192: [info] [314] close connection
2017/02/22 12:39:16 server.go:192: [info] [371] close connection
2017/02/22 12:39:16 server.go:192: [info] [369] close connection

客户端错误是这样的：

java.sql.SQLException: An attempt by a client to checkout a Connection has timed out.
	at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
	at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:65)
	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:527)
	at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
	at com.fancy.data.mysql.MysqlConnection.getConnection(MysqlConnection.java:67)
	at com.fancy.data.mysql.MysqlClient.getConnection(MysqlClient.java:32)
	at com.fancy.data.main.InsertMysql.run(InsertMysql.java:23)
	at com.fancy.data.backup.mysql.DealOneDayOneTable.flush(DealOneDayOneTable.java:206)
	at com.fancy.data.hbase.QueryHBase.runScan(QueryHBase.java:123)
	at com.fancy.data.backup.mysql.DealOneDayOneTable.run(DealOneDayOneTable.java:259)
	at java.lang.Thread.run(Thread.java:745)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: com.mchange.v2.resourcepool.TimeoutException: A client timed out while waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePool@5a52059c -- timeout at awaitAvailable()
	at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1317)
	at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
	at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)

	at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
	... 11 more
12:39:15,910 ERROR MysqlClient:35 - 获取数据库连接异常，程序退出
java.lang.NullPointerException
	at com.fancy.data.mysql.MysqlClient.getConnection(MysqlClient.java:33)
	at com.fancy.data.main.InsertMysql.run(InsertMysql.java:23)
	at com.fancy.data.backup.mysql.DealOneDayOneTable.flush(DealOneDayOneTable.java:206)
	at com.fancy.data.hbase.QueryHBase.runScan(QueryHBase.java:123)
	at com.fancy.data.backup.mysql.DealOneDayOneTable.run(DealOneDayOneTable.java:259)
	at java.lang.Thread.run(Thread.java:745)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

delete store. 被delete的store处于offline状态，多久会转为“完成下线”状态

有什么参数影响该时间吗？

TiDB 工具集是开源的吗？

A typo in README.md

In the section of "PD Server", the word "原信息" seems a typo for "元信息".

Not sure whether should I create an issue for such a question. -:(

使用loader 导入 mydumper导出文件，大写表名变成小写

如题，请教我使用loader导入mydumper导出的sql时，原来大写的表名会全部转换成小写，怎么样才能保持原来的大写表名？

用loader向MySQL导入数据时报错（mydumper导出的）

麻烦帮忙看看，报错日志如下：

017/07/08 16:47:11 main.go:47: [info] Config({FlagSet:0xc420164060 LogLevel:info LogFile: PprofAddr::10084 FileNumPerBlock:64 PoolSize:16 PoolCount:16 Dir:/data/cmbiData/cm_loan_7_8 CheckPoint:loader.checkpoint DB:{Host:10.47.20.105 User:datavalue_pro Password:murq6wmhqzp54v5kqk9v7za45xo1a5 Port:3306} configFile: SkipConstraintCheck:0})
2017/07/08 16:47:11 checkpoint.go:101: [info] calc checkpoint finished. finished tables (map[])
2017/07/08 16:47:11 loader.go:483: [info] [loader][run db schema]/data/cmbiData/cm_loan_7_8/cm_loan-schema-create.sql[start]
2017/07/08 16:47:11 loader.go:492: [info] [loader][run db schema]/data/cmbiData/cm_loan_7_8/cm_loan-schema-create.sql[finished]
2017/07/08 16:47:11 db.go:103: [error] exec set session.tidb_skip_constraint_check failed Error 1193: Unknown system variable 'tidb_skip_constraint_check'
2017/07/08 16:47:11 loader.go:517: [fatal] run table schema failed - Error 1193: Unknown system variable 'tidb_skip_constraint_check'
/home/jenkins/workspace/TIDB_TOOLS_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb-tools/loader/db.go:80:
/home/jenkins/workspace/TIDB_TOOLS_POST_COMMIT_FLOW/go/src/github.com/pingcap/tidb-tools/loader/loader.go:438:

命令行参数文档里面缺少 tidb 的 --skip-grant-table 参数说明

tidb-server 新增了 --skip-grant-table 参数，文档没有更新

权限管理已支持 hostname 前缀匹配，FAQ 文档没有更新

grant 权限时指定通配符匹配客户端 ip

PingCAP 团队技术博客链接地址 404

PingCAP 团队技术博客，现在是http://www.pingcap.com/bloglist.html，打开会显示404；
中文博客地址是https://pingcap.com/blog-add-a-built-in-function-zh.html
英文博客地址是https://pingcap.github.io/blog/

TiDB的容灾怎么实现？

TiDB有什么方式可在异地做同步？

TODO: refine TOC

current TOC is out of order. 😞

tikv docker start unfound listening port 20160

docker run -d --name pd1
-p 192.168.100.179:2379:2379
-p 192.168.100.179:2380:2380
-v /etc/localtime:/etc/localtime:ro
-v /data:/data
pingcap/pd:latest
--name="pd1"
--data-dir="/data/pd1"
--client-urls="http://0.0.0.0:2379"
--advertise-client-urls="http://192.168.100.179:2379"
--peer-urls="http://0.0.0.0:2380"
--advertise-peer-urls="http://192.168.100.179:2380"
--initial-cluster="pd1=http://192.168.100.179:2380"

and

docker run -d --name tikv1
-p 192.168.100.178:20160:20160
-v /etc/localtime:/etc/localtime:ro
-v /data:/data
pingcap/tikv:latest
--addr="192.168.100.178:20160"
--advertise-addr="192.168.100.178:20160"
--data-dir="/data/tikv1"
--pd="192.168.100.179:2379"
--log-file=tikv.log

less tikv.log
2017/07/03 18:01:32.768 tikv-server.rs:276: [WARN] Limit("kernel parameters net.core.somaxconn got 128, expect 32768")
2017/07/03 18:01:32.768 tikv-server.rs:276: [WARN] Limit("check_kernel_params failed No such file or directory (os error 2)")
2017/07/03 18:01:32.768 tikv-server.rs:276: [WARN] Limit("kernel parameters vm.swappiness got 60, expect 0")

but unfound20160 port

tidb also unfound 4000 port

and why?
(--sysctl net.core.somaxconn=32768 )

Configuration explanation needed

We need a detailed explanation in Chinese to describe TiDB/TiKV/PD's configurations.

Is there any way to show the log status of TiDB stuffs

If I run pd-server tikv-server and tidb-server with daemon mode,is there any way to show the log status of TiDB stuffs.And when I start a tidb-server with specific param "--store=tikv“,what is that mean?It must be the "tikv"? 3KS

pd-server: 通过jion方式加入出错

在新增pdserver过程中出错，pd member中出现片段信息（我这样理解，请包涵）。
而后继续增加该pd-server，报错： [fatal] join error etcdserver: re-configuration failed due to not enough started members。
pd-ctl member命令输出信息如下：

{
  "members": [
    {
      "member_id": 1989351853167724236,
      "peer_urls": [
        "http://192.168.20.157:2380"
      ]
    },
    {
      "name": "pd02",
      "member_id": 6114201539766314484,
      "peer_urls": [
        "http://192.168.20.158:2380"
      ],
      "client_urls": [
        "http://192.168.20.158:2379"
      ]
    },
    {

请问是等待一段时间后系统自行修复，还是需要额外做什么事情，以达到新增指定ip的pdserver？

在使用 loader 工具导入数据时，tidb_loader 库读写十分缓慢

日志中经常有 UPDATE tidb_loader.checkpoint 语句耗时一百秒以上。人工通过 mysql 客户端连接查询 tidb_loader 库也非常慢。这是什么原因？

部署集群拓扑是按照推荐的 6 台服务器，硬盘均为 SSD，看到监控中各个服务器的 CPU 和内存都没有被占满。

写入、更新数据就报错

按照文档推荐的Ansible 部署完之后，新建了一个数据库、表。对改表进行写入、新增时虽然内容会更新上去，但是就是会一直报错： line 0 column 12 near "" (total length 12)

pingcap / docs-cn Goto Github PK

docs-cn's Issues

Recommend Projects

Recommend Topics

Recommend Org