Release 0.14.0

[busbey]

follow up from #981. There's already a fair bit of churn on master in the ~9 months since the 0.13.0-staging branch started.

Additionally, we have a good deal of testing work left over that never happened in the 0.13.0 RC process.

[twblamer]

Just curious, what testing work is needed? Is this a matter of manually testing the bindings, the individual features/PRs, or both?

[busbey]

yep! we'll need to test a number of bindings and any specific fixes that are supposed to be present.

The first step is to get a list up of which bindings / features /etc. It's on my todo list, but I've been a bit swamped on a different project lately.

[busbey]

generally speaking, testing a binding should be straight forward. It's essentially:

1. Download RC and build binary bits
2. stand up an instance of whatever backing datastore (cluster deploy optimal, but single-node is fine)
3. follow the README for the specific binding for configuration
4. run the recommended sequence of workloads
5. post results here, with details about versions / sizes / etc.

using either the binding specific tarball or the omnibus is fine, but which one got used should probably be noted in the results.

[busbey]

waiting on these merges:

• [core] Fix ycsb.sh and ycsb.bat missing core dependencies #908
• [cassandra] Update CassandraCQLClient to use PreparedStatement for better performance #1051
• Kudu update #1098
• Update Bigtable client version to 1.3.0 (latest). #1147

[busbey]

merged #908

[busbey]

merged #1098 and #1147 .

looks like folks are in progress on #1051

[busbey]

would like to get #1148 "Update HBase 2 version to 2.0.0 GA" in for polish on the hbase addition

[busbey]

As a reminder, this release needs to cover essentially everything since 0.12.0. So the release notes will end up copying some things from the 0.13.0 release notes (like known incompatibilities)

This list of things to check presumes both #1148 and #1051 will land before I cut the feature branch.

New Topics

Needs a review because they'll get pushed in the release notes:

• We have a contributor guide for folks who want to get involved in YCSB! [core] Add a CONTRIBUTING.md file to fix #245. #1026
• Timeseries workload now added [core] Add the TimeSeriesWorkload class, a new type of workload that … #1008, [core][timeseries] Fix timestamp generation when one tag with cardinality one. #1091, [core] changes to enable folding YCSB-TS back into YCSB #1095

Datastore bindings that changed and will need to be tested to stay in the "verified" category

• Kudu [kudu] Update Kudu binding to 1.1.0, use slf4j for logging, improve table partitioning #879, Kudu update #1098
• Solr [solr,solr6] Add support for Kerberized Solr #887
• Solr6 [solr,solr6] Add support for Kerberized Solr #887
• Aerospike Change the write policy to REPLACE_ONLY #937
• Accumulo 1.6 A general "refresh" to the Accumulo binding #947, Switch Accumulo into multiple modules, one per minor release #1034, [accumulo] README was incorrectly referencing aerospike-binding #1056, [accumulo1.6, scripts] deprecate Accumulo 1.6 client, since Accumulo 1.6 is EOM. #1114
• Memcached w/binary protocol [memcached] support binary protocol #965
• Geode v1.2 and v1.3 [geode] Update to apache-geode 1.2.0 release #995, [geode] Ensure geode client will work with v1.3 by removing references to internal classes #1069
• s3 [s3] S3Client could not estimate read perfomance correctly (#994) #1010, [s3] Use AWS IOUtils to read object data #1021
• Google Datastore w/default credentials [googledatastore] Google Datastore to use default credentials. #984
• JDBC [jdbc] Use TEXT for fields instead of VARCHAR #910
• HBase 0.98 [hbase098] Fix #923 by interrupting the current thread. #1025, [hbase098, hbase10, hbase14, hbase20] HBase client updates #1113
• HBase 1.0 [hbase10] Address #701 by mimicking the same locks from the HBase 0.9… #1028, [hbase098, hbase10, hbase14, hbase20] HBase client updates #1113, [hbase10] Remove use of guava #1140
• Google Bigtable [googlebigtable] Upgrading googlebigtable to the latest version. #978, update bigtable to 1.0 #1070, Update Bigtable client version to 1.3.0 (latest). #1147
• MongoDB update mongodb-java-driver to latest 3.6.3 #1138
• Cassandra [cassandra] Update CassandraCQLClient to use PreparedStatement for better performance #1051

Newly added datastore bindings

• Azure DocumentDB [azuredocumentdb] Added support for Azure DocumentDB #838
• ArangoDB [arangodb3] added ArangoDB3 binding (ArangoDB 3.1, Java driver 4.1.7) #903
• Google Cloud Spanner [cloudspanner] Add YCSB Client for Google's Cloud Spanner. #939, updates to cloudspanner #998, [cloudspanner] Update Cloud Spanner Client Version to 0.21.1-beta #1007, Update Cloud Spanner Client version to 0.24.0-beta #1043
• HBase 1.2 [hbase12] Add HBase 1.2+ specific client that relies on the shaded client artifact provided by those versions. #970, [hbase10] Remove use of guava #1140
• HBase 1.4 [hbase098, hbase10, hbase14, hbase20] HBase client updates #1113, [hbase10] Remove use of guava #1140
• HBase 2.0 [hbase098, hbase10, hbase14, hbase20] HBase client updates #1113, [hbase10] Remove use of guava #1140, [hbase20] update hbase 2 version to 2.0.0 GA #1148
• Accumulo 1.7 Switch Accumulo into multiple modules, one per minor release #1034
• Accumulo 1.8 Switch Accumulo into multiple modules, one per minor release #1034
• Elastic Search 5 standard workloads [elasticsearch,elasticsearch5] Add Elasticsearch 5.x binding #925
• MaprDB Added clients for MapR-DB and MapR-JSONDB #1063
• MaprJSONDB Added clients for MapR-DB and MapR-JSONDB #1063

Issues with core

• run from source check out via scripts rather than python [core] Fix ycsb.sh and ycsb.bat missing core dependencies #908

[busbey]

Another modified store I just merged:

• Redis (plain and cluster mode) Redis cluster support #1072

[busbey]

found some headers missing before making the staging branch. put up #1150 to fix it.

[twblamer]

Looks like the two output fixes that were done for 0.13.0 aren't present in master: 88ffdbb and 46933b1

[busbey]

excellent catch!

[busbey]

okay I cherry-pick #1060, #1084, and #1085 to the master branch.

[busbey]

Release candidate 1 is up: https://github.com/brianfrankcooper/YCSB/releases/tag/0.14.0-RC1

[robertpang]

@busbey Just tested 0.14.0-RC1 with Apache Cassandra and @YugaByte datastores with no issue. Here are the test config and results:

Datastore setup:

• 3-node cluster on Google Cloud Platform
• Each node is a n1-standard-16 in same availability zone with:
  • 16 vcpu’s, Intel® Xeon® CPU @ 2.20GHz CPUs
  • 60GB RAM
  • 2 x 375 GB direct attached SSD
  • OS: CentOS 7.5

YCBS client setup:

• n1-standard-4 in the same availability zone

YCSB workload parameters:

• recordcount=1000000
• operationcount=10000000
• maxexecutiontime=180
• threadcount=256
• cassandra.readconsistencylevel=QUORUM
• cassandra.writeconsistencylevel=QUORUM

Apache Cassandra config:

• cassandra-3.11.2-1.noarch.rpm
• Garbage collector: G1GC
• MAX_HEAP_SIZE: 12GB

Results:
workloada-transaction.dat:[OVERALL], Throughput(ops/sec), 66747.20829801293
workloadb-transaction.dat:[OVERALL], Throughput(ops/sec), 51192.273091312025
workloadc-transaction.dat:[OVERALL], Throughput(ops/sec), 54417.28508822448
workloadd-transaction.dat:[OVERALL], Throughput(ops/sec), 66660.44502513099
workloade-transaction.dat:[OVERALL], Throughput(ops/sec), 8650.39383899774
workloadf-transaction.dat:[OVERALL], Throughput(ops/sec), 35613.0058469268

YugaByte DB config:

• v1.0.0 release
• Client driver:
  • groupId: com.yugabyte
  • artifactId: cassandra-driver-core
  • version: 3.2.0-yb-12

Results:
workloada-transaction.dat:[OVERALL], Throughput(ops/sec), 72913.93239420188
workloadb-transaction.dat:[OVERALL], Throughput(ops/sec), 75755.85403362045
workloadc-transaction.dat:[OVERALL], Throughput(ops/sec), 72795.03829019015
workloadd-transaction.dat:[OVERALL], Throughput(ops/sec), 70898.85569246912
workloade-transaction.dat:[OVERALL], Throughput(ops/sec), 14612.108483944552
workloadf-transaction.dat:[OVERALL], Throughput(ops/sec), 50118.351472330716

Please let me know if you need more details or the full output log.

[busbey]

Thanks @robertpang! that'll do nicely.

[busbey]

I sent pings for testing to the user@ lists for:

• Apache HBase
• Apache Geode
• Apache Accumulo
• Apache Kudu
• Apache Solr

[busbey]

known issues for this release should include #1155

[metatype]

@upthewaterspout and I tested the Geode datastore versions 1.2.0, 1.3.0, and 1.6.0 (latest) against the Geode driver. Everything looks good!

[busbey]

thanks geode folks!

[fwang29]

I tested 0.14.0-RC1 with Kudu (single node) on CentOS 6.6 and tweaked with some workload parameters as below:
kudu_buffer_num_ops=1000
kudu_block_size=2048
kudu_table_num_replicas=1

Nothing looks wrong!

[busbey]

thanks @fwang29! what version of Kudu did you use?

[fwang29]

@busbey NP! Sorry, I forgot to mention it. It was version 1.8.0.

[twblamer]

I tested the mongodb binding and had no issues.

YCSB build:

• Binding specific tarball (ycsb-mongodb-binding-0.14.0-RC2-SNAPSHOT.tar.gz)

Host details:

• 2 Intel Xeon CPU E5-2690 v4 @ 2.60GHz (28 threads / 14 cores each)
• 256 GB RAM
• 1600 GB NVMe SSD
• OS: Fedora 25
• Java version: OpenJDK 8 (java-1.8.0-openjdk-1.8.0.151-1.b12.fc25.x86_64)

Client details:

• YCSB client executed on same host as DB

Database setup:

• MongoDB Community Server 3.6.4 (mongodb-org-server-3.6.4-1.el7.x86_64)
• WiredTiger storage engine
• Standalone database (no replication or sharding)

YCSB workload parameters:

• recordcount=100000000
• operationcount=100000000
• threadcount=64

Disclaimer: this was and a "fire and forget" run with no tuning

Results for mongodb client

./load1.result.txt:         [OVERALL], Throughput(ops/sec), 188692.0621023315
./workloada.result.txt:     [OVERALL], Throughput(ops/sec), 48469.972609618475
./workloadb.result.txt:     [OVERALL], Throughput(ops/sec), 178248.0357066465
./workloadc.result.txt:     [OVERALL], Throughput(ops/sec), 250913.95407772812
./workloadf.result.txt:     [OVERALL], Throughput(ops/sec), 45878.48349590374
./workloadd.result.txt:     [OVERALL], Throughput(ops/sec), 247723.42175408002
./load2.result.txt:         [OVERALL], Throughput(ops/sec), 119994.28827187826
./workloade.result.txt:     [OVERALL], Throughput(ops/sec), 29943.45477999346

Results for mongodb-async client

./load1.result.txt:         [OVERALL], Throughput(ops/sec), 45912.81798643827
./workloada.result.txt:     [OVERALL], Throughput(ops/sec), 24325.67407050991
./workloadb.result.txt:     [OVERALL], Throughput(ops/sec), 56964.15245885764
./workloadc.result.txt:     [OVERALL], Throughput(ops/sec), 72597.38939787725
./workloadf.result.txt:     [OVERALL], Throughput(ops/sec), 24995.731978764627
./workloadd.result.txt:     [OVERALL], Throughput(ops/sec), 70591.75657703396
./load2.result.txt:         [OVERALL], Throughput(ops/sec), 43336.09962102581
./workloade.result.txt:     [OVERALL], Throughput(ops/sec), 5611.603314190471

[busbey]

I'd like to wrap up this RC by the end of the week. Thanks so much to the folks who have tested things so far!

IMHO we already have enough tested datastore bindings to close things out. Since I have most of the testing for the Apache HBase related changes done, I think I'll make a go of finishing that up before closing things up.

I can test out that basics work on windows as well, unless someone else wants to take it on.

Bindings currently slated to be listed as "untested / your milage may vary", with a ping to folks who showed up on related PRs:

• Accumulo 1.6, 1.7, 1.8 (@joshelser @phrocker @hinchliff @ctubbsii have time to take a look?)
• Aerospike (@tiboratAS have time to take a look?)
• Azure DocumentDB (@k1xme have time to take a look?)
• ArangoDB3 ( @mpv1989 @diogojfernandes have time to take a look?)
• Elastic Search 5 ( @risdenk @jasontedor @levaphenyl have time to take a look?)
• Google Bigtable (@sduskis @igorbernstein2 @mbrukman have time to take a look?)
• Google Cloud Spanner (@siamaktz @samizuh @hostirosti have time to take a look?)
• Google Datastore (@haih-g have time to take a look?)
• JDBC (@k1xme @risdenk have time to take a look?)
• MaprDB, MaprJSONDB(@rohanjayaraj have time to take a look?)
• Memcached (@solganik have time to take a look?)
• Redis (@j3ns have time to take a look?)
• s3 (@bosher @risdenk have time to take a look?)
• Solr, Solr6 (@risdenk have time to take a look?)

[haihuang-google]

Google Datastore

I have this continuously running in our test environment and see no problem.

[busbey]

@haih-g could you have it test specifically against the 0.14.0-RC1 tag?

[isuntsov-gridgain]

@busbey where I can get the actual list of untested bindings?

[busbey]

My comment from ~3 days ago is still fairly up to date. IIRC, only Google Datastore has since been tested.

I'm probably only going to test the HBase 1.2+ bindings, which would mean HBase 0.98 and HBase 1.0 will also go into the list.

Is that what you're looking for @isuntsov-gridgain?

[ctubbsii]

Although I was tagged, I won't be able to test the Accumulo bindings without detailed step-by-step instructions... I'm not a YCSB user and know next to nothing about YCSB. However, with detailed step-by-step testing instructions, I'd happily launch an Accumulo instance to test against.

[joshelser]

@ctubbsii see the README, e.g https://github.com/brianfrankcooper/YCSB/tree/master/accumulo1.8. It's very straightforward. Just "load" and then "test" for a workload. Testing one is likely "good enough" (you don't need to do workloads A through F).

[ctubbsii]

@joshelser Thanks. I didn't realize there was a README in the subdirectory with detailed instructions. Will use those. 😺

[bosher]

Hi Sean, I have tested my s3 changes with 0.14.0 RC1. My testing have not revealed any problems. Best regards, Boris Osher (408) 368-9089

…

On Mon, Jun 4, 2018 at 10:26 AM, Sean Busbey ***@***.***> wrote: I'd like to wrap up this RC by the end of the week. Thanks so much to the folks who have tested things so far! IMHO we already have enough tested datastore bindings to close things out. Since I have most of the testing for the Apache HBase related changes done, I think I'll make a go of finishing that up before closing things up. I can test out that basics work on windows as well, unless someone else wants to take it on. Bindings currently slated to be listed as "untested / your milage may vary", with a ping to folks who showed up on related PRs: - Accumulo 1.6, 1.7, 1.8 ***@***.*** <https://github.com/joshelser> @phrocker <https://github.com/phrocker> @hinchliff <https://github.com/hinchliff> @ctubbsii <https://github.com/ctubbsii> have time to take a look?) - Aerospike ***@***.*** <https://github.com/tiboratAS> have time to take a look?) - Azure DocumentDB ***@***.*** <https://github.com/k1xme> have time to take a look?) - ArangoDB3 ( @mpv1989 <https://github.com/mpv1989> @diogojfernandes <https://github.com/diogojfernandes> have time to take a look?) - Elastic Search 5 ( @risdenk <https://github.com/risdenk> @jasontedor <https://github.com/jasontedor> @levaphenyl <https://github.com/levaphenyl> have time to take a look?) - Google Bigtable ***@***.*** <https://github.com/sduskis> @igorbernstein2 <https://github.com/igorbernstein2> @mbrukman <https://github.com/mbrukman> have time to take a look?) - Google Cloud Spanner ***@***.*** <https://github.com/siamaktz> @samizuh <https://github.com/samizuh> @hostirosti <https://github.com/hostirosti> have time to take a look?) - Google Datastore ***@***.*** <https://github.com/haih-g> have time to take a look?) - JDBC ***@***.*** <https://github.com/k1xme> @risdenk <https://github.com/risdenk> have time to take a look?) - MaprDB, ***@***.*** <https://github.com/rohanjayaraj> have time to take a look?) - Memcached ***@***.*** <https://github.com/solganik> have time to take a look?) - Redis ***@***.*** <https://github.com/j3ns> have time to take a look?) - s3 ***@***.*** <https://github.com/bosher> @risdenk <https://github.com/risdenk> have time to take a look?) - Solr, Solr6 ***@***.*** <https://github.com/risdenk> have time to take a look?) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1117 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABXzlYhNxXlK2OXQSM0uy9QHa-_Kgn4rks5t5W3DgaJpZM4S-Bxn> .

[ctubbsii]

Issues I found testing Accumulo 1.9.1:

1. The build has an error: no version specified for apache-rat-plugin (see PR [build] Add missing version to rat plugin #1168)
2. accumulo.1.7.version should be 1.7.4 (see PR [accumulo] Use latest versions of Accumulo #1167)
3. accumulo.1.8.version should be 1.9.1 (see PR [accumulo] Use latest versions of Accumulo #1167) (yes, 1.9.1, not 1.8.1; 1.8.0 and 1.8.1 had critical data loss issues; 1.9.x replaces the 1.8 series)

I'm not sure what to look for in the testing output, but everything seemed to work fine if I set accumulo.1.8.version to 1.9.1 and ran load, followed by run, according to the accumulo1.8 README.

I tested using https://github.com/apache/fluo-uno using workload A on a single machine, with Apache Accumulo 1.9.1, Apache Hadoop 2.7.6, and Apache ZooKeeper 3.4.12

[busbey]

are the Accumulo version numbers needed for the release or would they be fine to update for next time?

[ctubbsii]

I think the main risk with releasing without the updated Accumulo version numbers is possible confusion. I would rate the risk low.

[isuntsov-gridgain]

@busbey actually I'm not familiar with any distributed systems from this list so it will be the random choice.
I've started to work with Aerospike.

[isuntsov-gridgain]

Guys,

I see in YCSB/pom.xml (0.14.0-staging):
<aerospike.version>3.1.2</aerospike.version>

It is a version that was released in 2014. With the 4.1+ I have compilation problems. Is it OK?

[busbey]

I see in YCSB/pom.xml (0.14.0-staging):
<aerospike.version>3.1.2</aerospike.version>

It is a version that was released in 2014. With the 4.1+ I have compilation problems. Is it OK?

If it works with the version advertised in YCSB then it's okay for the release. if things are tested then we expressly call out what version(s) were tested for the release notes. ("advertised" here means either a) mentioned in the README, b) mentioned in prior release notes, c) version in the pom

For this sort of thing usually I'd suggest making sure there's a ticket about needing to update. Or if you want to and have time to fix it now just start with a PR. We can include an update in the next release. I'd look for feedback from whoever maintains Aerospike about wether it's worth keeping compatibility with both v3 and v4.

[rohanjayaraj]

@busbey Tested 0.14.0-RC1 with MapR-DB and MapR-JSONDB datastores and found no issues. Below are the configs and results :

Datastore setup

• single node cluster
• 20 CPUs, Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
• 256GB RAM
• 5 x 450GB Samsung MKZ SSD
• OS: CentOS 7.4

YCBS client setup

• YCSB client executed on the same node

YCSB workload parameters

• recordcount=10000000
• operationcount=10000000
• threadcount=32

MapR Database Setup

• MapR Converged Community Edition 6.0.1

Results for maprdb client

load1:       [OVERALL], Throughput(ops/sec), 121410.793419535
workloada:     [OVERALL], Throughput(ops/sec), 135895.41488870166
workloadb:     [OVERALL], Throughput(ops/sec), 81240.70809401174   
workloadc:     [OVERALL], Throughput(ops/sec), 79145.23149980213
workloadf:      [OVERALL], Throughput(ops/sec), 68762.54916522265
workloadd:     [OVERALL], Throughput(ops/sec), 83941.91219675985
load2:       [OVERALL], Throughput(ops/sec), 133481.05236461683
workloade:     [OVERALL], Throughput(ops/sec), 8598.895901766213

Results for maprjsondb client

load1:       [OVERALL], Throughput(ops/sec), 147240.70911125507
workloada:      [OVERALL], Throughput(ops/sec), 87088.29010851201
workloadb:      [OVERALL], Throughput(ops/sec), 70698.35838411831
workloadc:      [OVERALL], Throughput(ops/sec), 76678.29620825825
workloadf:      [OVERALL], Throughput(ops/sec), 37459.216278277025
workloadd:     [OVERALL], Throughput(ops/sec), 68926.5380956976
load2:       [OVERALL], Throughput(ops/sec), 162593.6946165228
workloade:     [OVERALL], Throughput(ops/sec), 9972.575417601596

[isuntsov-gridgain]

I've finished with Aerospike.
Environment:

• Ubuntu 16.04
• CPUs: 8
• RAM: 32
• SSD: 400 GiB

YCBS client setup

• YCSB client executed on the same node

Aerospike server version: 4.2.0.3

Results for Aerospike client:
load: [OVERALL], Throughput(ops/sec), 4651.162790697675
workloadb: [OVERALL], Throughput(ops/sec), 4739.336492890995
workloadc: [OVERALL], Throughput(ops/sec), 5464.48087431694
workloadf: [OVERALL], Throughput(ops/sec), 4310.3448275862065
workloadd: [OVERALL], Throughput(ops/sec), 4926.108374384236

[isuntsov-gridgain]

Redis - done!
Version: 4.0.9
Environment:

• mac os
• RAM: 16g
• CPU: 8

YCBS client setup

• YCSB client executed on the same node

load
[OVERALL], Throughput(ops/sec), 427.53313381787086

run
a [OVERALL], Throughput(ops/sec), 4901.9607843137255
b [OVERALL], Throughput(ops/sec), 4975.124378109453
c [OVERALL], Throughput(ops/sec), 5128.205128205128
d [OVERALL], Throughput(ops/sec), 4739.336492890995
f [OVERALL], Throughput(ops/sec), 3968.253968253968

[busbey]

in evaluating the RC I found that the big tarball doesn't have a README.md included, filed #1171. It's been broken for ~4 years so I don't think it needs to be fixed for this release. someone shout if they'd prefer otherwise.

[busbey]

the hbase098 binding instructions refer to a binding that doesn't exist instead of hbase098. filed #1172. I don't think this should be a blocker.

[busbey]

tested against HBase 1.2 (CDH 5.14.2) (via hbase098, hbase10, hbase12, hbase14, and hbase20 bindings)

found #1173 [hbase20] no slf4j implementation; hbase client doesn't log. it doesn't seem like a blocker, since none of the information we miss from logging is critical and it can be worked around by adding an slf4j logging-binding to the classpath.

[busbey]

tested against HBase 2.0 (CDH 6.0.0-beta1) (via hbase10, hbase12, hbase14, and hbase20 bindings)

#1173 applies there too.

[busbey]

draft release notes: https://gist.github.com/busbey/9170b4d5f82b7be215d846f4b0a5d398

[petersomogyi]

@busbey: release notes is great! I have 2 minor comments:

• Typo: implementerd
• 2 #s: (see # [hbase20] no slf4j implementation; hbase client doesn't log #1173)

[busbey]

Thanks @petersomogyi! I've corrected both of those now.

[jojochuang]

@busbey thanks a lot for the release note!
I spotted one typo: doesn't "prior" log --> provide

[busbey]

good catch @jojochuang! fixed now. thanks.

[busbey]

Unless anyone else has something they'd like to see changed, I plan to push the release in about an hour, FYI.

[busbey]

release is up: https://github.com/brianfrankcooper/YCSB/releases/tag/0.14.0

[busbey]

PR up to point folks to the new release from our landing page: #1174 . if someone could take a look please.

[busbey]

Closing this release out. I don't have the time ATM to do release announcements across the various mailing lists. If anyone else wants to pick that up let me know and I'll point you at the template.