A Java client for TiDB/TiKV. It is supposed to:
- Communicate via gRPC
- Talk to Placement Driver searching for a region
- Talk to TiKV for reading/writing data and the resulted data is encoded/decoded just like what we do in TiDB.
- Talk to Coprocessor for calculation pushdown
The alternative way to build a usable jar for testing will be
mvn clean install -Dmaven.test.skip=true
The following command can install dependencies for you.
mvn package
The jar can be found in ./target/
This project is designed to hook with pd and tikv.
When you work with this project, you have to communicate with pd and tikv. Please run TiKV and PD in advance.
Java Implementation of Raw TiKV-Client to support RawKVClient commands.
Demo is avaliable in KVRawClientTest
mvn clean install -Dmaven.test.skip=true
Add your jar built with all dependencies into you project's library to use tikv-client-java as dependency
After building, add following lines into your pom.xml if you are using Maven
<dependency>
<groupId>org.tikv</groupId>
<artifactId>tikv-client-java</artifactId>
<version>3.1.0</version>
</dependency>org.tikv.raw.RawKVClient
import org.tikv.common.TiConfiguration;
import org.tikv.common.TiSession;
import org.tikv.raw.RawKVClient;
public class Main {
public static void main() {
// You MUST create a raw configuration if you are using RawKVClient.
TiConfiguration conf = TiConfiguration.createRawDefault(YOUR_PD_ADDRESSES);
TiSession session = TiSession.create(conf);
RawKVClient client = session.createRawClient();
}
}The following includes JVM related parameters.
- pd addresses, separated by comma
- default: 127.0.0.1:2379
- timeout of grpc request
- default: 600ms
- timeout of scan/delete range grpc request
- default: 20s
- Maximal package size transporting from clients to TiKV Server (ingest API)
- default: 1048576 (1M)
- Maximal batch size transporting from clients to TiKV Server (ingest API)
- default: 32768 (32K)
- time to wait for scattering regions
- default: 300 (5min)
- RawKV default backoff in milliseconds
- default: 20000 (20 seconds)
- whether to enable metrics exporting
- default: false
- the metrics exporting http port
- default: 3140
The following includes ThreadPool related parameters, which can be passed in through JVM parameters.
- the thread pool size of batchGet on client side
- default: 20
- the thread pool size of batchPut on client side
- default: 20
- the thread pool size of batchDelete on client side
- default: 20
- the thread pool size of batchScan on client side
- default: 5
- the thread pool size of deleteRange on client side
- default: 20
- whether to enable
Compare And Set, set true if usingRawKVClient.compareAndSetorRawKVClient.putIfAbsent - default: false
Client Java supports exporting metrics to Prometheus using poll mode and viewing on Grafana. The following steps shows how to enable this function.
- set the config
tikv.metrics.enabletotrue - call TiConfiguration.setMetricsEnable(true)
- set the config
tikv.metrics.port - call TiConfiguration.setMetricsPort
Default port is 3140.
Add the following config to conf/prometheus.yml and restart Prometheus.
- job_name: "tikv-client"
honor_labels: true
static_configs:
- targets:
- '127.0.0.1:3140'
- '127.0.0.2:3140'
- '127.0.0.3:3140'Import the Client-Java-Summary dashboard config to Grafana.
Apache 2.0 license. See the LICENSE file for details.