Tidb 单机安装

Tidb单机版只能用于验证学习，生产环境是肯定不能用单机版的。

首先二进制版下载

wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz

然后解压

tar -xzvf  tidb-latest-linux-amd64.tar.gz

cd tidb-latest-linux-amd64/bin

启动pd命令

./bin/pd-server --data-dir=pd-data

2018/04/19 22:01:28.138 log.go:84: [info] embed: [serving insecure client requests on 127.0.0.1:2379, this is strongly discouraged!]
2018/04/19 22:01:28.140 server.go:198: [info] init cluster id 6546388963250910576
2018/04/19 22:01:28.140 leader.go:89: [warning] leader is still name:"pd" member_id:13195394291058371180 peer_urls:"http://127.0.0.1:2380" client_urls:"http://127.0.0.1:2379" , delete and campaign again
2018/04/19 22:01:28.144 tso.go:104: [info] sync and save timestamp: last 2018-04-19 22:01:18.984387626 -0700 PDT save 2018-04-19 22:01:31.14395005 -0700 PDT m=+7.041048006
2018/04/19 22:01:28.144 leader.go:269: [info] PD cluster leader pd is ready to serve

启动 TiKV

./bin/tikv-server --pd="127.0.0.1:2379"   --store=tikv-data

2018/04/19 22:19:01.755 tikv-server.rs:215: [INFO] start storage
2018/04/19 22:19:01.755 mod.rs:346: [INFO] starting working thread: split check worker
2018/04/19 22:19:01.768 mod.rs:346: [INFO] starting working thread: snapshot worker
2018/04/19 22:19:01.770 mod.rs:346: [INFO] starting working thread: raft gc worker
2018/04/19 22:19:01.774 mod.rs:346: [INFO] starting working thread: compact worker
2018/04/19 22:19:01.776 future.rs:142: [INFO] starting working thread: pd worker
2018/04/19 22:19:01.779 mod.rs:346: [INFO] starting working thread: consistency check worker
2018/04/19 22:19:01.782 mod.rs:346: [INFO] starting working thread: cleanup sst worker
2018/04/19 22:19:01.782 mod.rs:346: [INFO] starting working thread: storage-scheduler
2018/04/19 22:19:01.782 mod.rs:346: [INFO] starting working thread: apply worker
2018/04/19 22:19:01.785 store.rs:597: [WARN] set priority for raftstore failed, error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
2018/04/19 22:19:01.787 mod.rs:346: [INFO] starting working thread: end-point-worker
2018/04/19 22:19:01.788 mod.rs:346: [INFO] starting working thread: snap-handler
2018/04/19 22:19:01.802 server.rs:169: [INFO] TiKV is ready to serve
2018/04/19 22:19:04.119 util.rs:79: [INFO] heartbeat receiver is refreshed.
2018/04/19 22:19:04.119 client.rs:318: [INFO] heartbeat sender is refreshed.
2018/04/19 22:19:04.119 client.rs:337: [ERROR] failed to send heartbeat: Grpc(RpcFinished(Some(RpcStatus { status: Ok, details: None })))
2018/04/19 22:19:04.119 util.rs:264: [ERROR] request failed: Grpc(RpcFinished(Some(RpcStatus { status: Ok, details: None })))
2018/04/19 22:19:04.120 util.rs:264: [ERROR] request failed: Other(SendError("..."))
2018/04/19 22:19:04.120 util.rs:264: [ERROR] request failed: Other(SendError("..."))
2018/04/19 22:19:04.120 util.rs:236: [WARN] updating PD client, block the tokio core
2018/04/19 22:19:04.120 util.rs:385: [INFO] connect to PD endpoint: "http://127.0.0.1:2379"
2018/04/19 22:19:04.122 util.rs:385: [INFO] connect to PD endpoint: "http://127.0.0.1:2379"
2018/04/19 22:19:04.123 util.rs:443: [INFO] connect to PD leader "http://127.0.0.1:2379"
2018/04/19 22:19:04.123 util.rs:179: [WARN] heartbeat sender and receiver are stale, refreshing..
2018/04/19 22:19:04.123 util.rs:198: [WARN] updating PD client done, spent Duration { secs: 0, nanos: 3661695 }
2018/04/19 22:19:04.123 client.rs:318: [INFO] heartbeat sender is refreshed.
2018/04/19 22:19:04.124 util.rs:79: [INFO] heartbeat receiver is refreshed.
2018/04/19 22:19:04.124 cache.go:419: [info] [region 2] Leader changed from {<nil>} to {id:3 store_id:1 }
2018/04/19 22:19:04.746 coordinator.go:193: [info] coordinator: Cluster information is prepared
2018/04/19 22:19:04.746 coordinator.go:203: [info] coordinator: Run scheduler
2018/04/19 22:19:04.746 coordinator.go:215: [info] create scheduler balance-region-scheduler
2018/04/19 22:19:04.746 coordinator.go:215: [info] create scheduler balance-leader-scheduler
2018/04/19 22:19:04.746 coordinator.go:215: [info] create scheduler balance-hot-region-scheduler
2018/04/19 22:19:04.746 coordinator.go:215: [info] create scheduler label-scheduler
2018/04/19 22:19:04.748 coordinator.go:136: [info] coordinator: start patrol regions

启动TiDB

./bin/tidb-server --store=tikv   --path="127.0.0.1:2379"

2018/04/19 22:28:01.898 ddl_worker.go:217: [info] [ddl] finish DDL job ID:28, Type:create table, State:synced, SchemaState:public, SchemaID:3, TableID:27, RowCount:0, ArgLen:0, start time: 2018-04-19 22:28:01.683 -0700 PDT, Err:<nil>, ErrCount:0, SnapshotVersion:0
2018/04/19 22:28:01.907 ddl.go:465: [info] [ddl] DDL job 28 is finished
2018/04/19 22:28:01.907 domain.go:406: [info] [ddl] on DDL change, must reload
2018/04/19 22:28:01.985 manager.go:234: [warning] [ddl] /tidb/ddl/fg/owner ownerManager 86470628-b3a0-49a5-a125-cf0b199e7248 isn't the owner
2018/04/19 22:28:01.988 manager.go:245: [info] [ddl] /tidb/ddl/fg/owner ownerManager 86470628-b3a0-49a5-a125-cf0b199e7248 break campaign loop, revoke err <nil>
2018/04/19 22:28:01.989 delete_range.go:105: [info] [ddl] closing delRange session pool
2018/04/19 22:28:01.989 ddl.go:344: [info] close DDL:86470628-b3a0-49a5-a125-cf0b199e7248
2018/04/19 22:28:01.989 ddl.go:307: [info] stop DDL:86470628-b3a0-49a5-a125-cf0b199e7248
2018/04/19 22:28:01.989 tidb.go:64: [info] store tikv-6546388963250910576 new domain, ddl lease 45s, stats lease 3000000000
2018/04/19 22:28:01.990 ddl.go:289: [info] [ddl] start delRangeManager OK, with emulator: false
2018/04/19 22:28:01.993 ddl.go:297: [info] [ddl] start DDL:095388fd-9af9-4d98-b8e8-0756504fc38f
2018/04/19 22:28:01.994 ddl_worker.go:71: [info] [ddl] cleaning jobs in the adding index queue finished.
2018/04/19 22:28:01.997 manager.go:269: [info] [ddl] /tidb/ddl/fg/owner ownerManager 095388fd-9af9-4d98-b8e8-0756504fc38f, owner is 095388fd-9af9-4d98-b8e8-0756504fc38f
2018/04/19 22:28:02.006 domain.go:117: [info] [ddl] full load InfoSchema from version 0 to 14, in 7.154842ms
2018/04/19 22:28:02.007 domain.go:309: [info] [ddl] full load and reset schema validator.
2018/04/19 22:28:02.024 gc_worker.go:131: [info] [gc worker] 58b86183afc0008 start.
2018/04/19 22:28:02.027 manager.go:269: [info] [stats] /tidb/stats/owner ownerManager 095388fd-9af9-4d98-b8e8-0756504fc38f, owner is 095388fd-9af9-4d98-b8e8-0756504fc38f
2018/04/19 22:28:02.030 simple.go:125: [info] [0] execute rollback statement
2018/04/19 22:28:02.030 txn.go:208: [info] [kv] Rollback txn 399560430579351563
2018/04/19 22:28:02.043 domain.go:645: [info] [stats] init stats info takes 19.234689ms
2018/04/19 22:28:02.081 server.go:189: [warning] Secure connection is NOT ENABLED
2018/04/19 22:28:02.081 server.go:156: [info] Server is running MySQL Protocol at [0.0.0.0:4000]
2018/04/19 22:28:02.081 main.go:186: [info] disable Prometheus push client
2018/04/19 22:28:02.081 http_status.go:74: [info] Listening on :10080 for status and metrics report.
2018/04/19 22:28:02.082 systime_mon.go:24: [info] start system time monitor
2018/04/19 22:28:10.320 apply.rs:902: [INFO] [region 4] 5 execute admin command cmd_type: CompactLog compact_log {compact_index: 109 compact_term: 6} at [term: 6, index: 111]

启动mysql客户端验证

mysql -h 127.0.0.1 -P 4000 -u root -D test

ok，tidb单机开发环境就弄好了。

像mysql一样，创建个用户，可以从任何主机登陆

create user 'peidw'@'%' identified by 'peidw'

赋个权

GRANT ALL ON *.* TO 'peidw'@'%';

就可以用自己建的用户连接tidb