Server raises `Sync` unimplemented and ycsb-t stucks before finishing

[molamooo]

Is it normal that server raise sync unimplemented when there is no client? I'm running 1 shard with 3 replicas on one machine at different port using

~/tapir/store/tapirstore/server -m txn-l -c ~/tapir/store/tools/shard0.config -i 2

However if I start ycsb-t client in time, the server stays.

Also, when I testing ycsb-t with 3 shards, 9 replicas in total, the throughput kept decreasing, and in the and the throughput reaches 0 with operationcount=1000000 not finished:

80 sec: 903644 operations; 0 current ops/sec; 
90 sec: 903644 operations; 0 current ops/sec; 
100 sec: 903644 operations; 0 current ops/sec;
110 sec: 903644 operations; 0 current ops/sec;
120 sec: 903644 operations; 0 current ops/sec;
130 sec: 903644 operations; 0 current ops/sec;
140 sec: 903644 operations; 0 current ops/sec;
150 sec: 903644 operations; 0 current ops/sec;
160 sec: 903644 operations; 0 current ops/sec;
170 sec: 903644 operations; 0 current ops/sec;
180 sec: 903644 operations; 0 current ops/sec;

Am I missing anything?

[irodotos]

5 years later i have the same question about the sync function