Pegasus Java Client

Build

cd scripts && sh recompile_thrift.sh && cd -
mvn spotless:apply
mvn clean package -DskipTests

Install

cd scripts && sh recompile_thrift.sh && cd -
mvn spotless:apply
mvn clean install -DskipTests

Test

To run test, you should start pegasus onebox firstly, and run test as:

cd scripts && sh recompile_thrift.sh && cd -
mvn spotless:apply
mvn clean package

or specify one test:

cd scripts && sh recompile_thrift.sh && cd -
mvn spotless:apply
mvn clean package -Dtest=TestPing

Configuration

Configure client by “pegasus.properties”, for example:

meta_servers = 127.0.0.1:34601,127.0.0.1:34602,127.0.0.1:34603
operation_timeout = 1000
async_workers = 4
enable_perf_counter = true
perf_counter_tags = k1=v1,k2=v2,k3=v3
push_counter_interval_secs = 10

You can provide a parameter of ‘configPath’ when creating a client instance.

The format of ‘configPath’ should be one of these:

zk path: zk://host1:port1,host2:port2,host3:port3/path/to/config
local file path: file:///path/to/config
resource path: resource:///path/to/config

PerfCounter(Metrics)

Pegasus Java Client supports QPS and latency statistics of requests.

The related configurations are:

enable_perf_counter = true
perf_counter_tags = k1=v1,k2=v2,k3=v3
push_counter_interval_secs = 10

For each type of request(get, set, multiset, etc.), we collect 8 metrics:

cps-1sec: the request's qps
cps-1min: the request's queries per 1 minute
cps-5min: the request's queries per 5 minutes
cps-15min: the request's queries per 15 minutes
latency-p50: the moving median of request's queries
latency-p99: the moving p99 of request's queries
lantecy-p999: the moving p999 of request‘s queries 8: latency-max: the moving max of request’s queries

We use io.dropwizard.metrics library to calculate the request count.

Currently, metrics are integrated with open-falcon(https://open-falcon.org/),

which push counters to local http agent http://127.0.0.1:1988/push/v1.

If you'd like to integrate pegasus client with other monitor system, please let us know ASAP.