Release 0.17.0

[busbey]

• update for move to groupId site.ycsb ❗️ in prep for publishing to maven central (Publish YCSB on Maven Central #1340)
• HBase bindings changed API for table checks ([hbase10] Use Admin.tableExists instead of Table.getTableDescriptor t… #1315) and fixed doc for skipping WAL writes (Adally update readme #1324)
• Number of threads used by client is capped by number of operations ([core] limit number of client threads based on op count. #1323)
• JDBC binding now works with mssql ([jdbc] Add mssql support for scan operation #1350) and uses semicolon for sharding ❗️ (Changed JDBC string splitting delimiter #1233)
• Added VoltDB binding ([db voltdb] Add VoltDB client #1319)

changes from 0.16.0 (#1265) that need testing:

core changes

• Allow configuration of field names via fieldnameprefix property (Added fieldnameprefix property #117)
• JDK 8 or 11 should be used, we no longer test JDK9 or JDK10 ([travis] drop deprecated oracle JDKs, add openjdk versions for jdk8 and jdk11 #1253)
• Improvements to some internal byte iterators (notably Strings) ([core] Optimize toArray of all ByteIterators except RandomByteIterator #1112)
• Correct configuration of exponential distribution in the Core workloads (Enabling exponential distribution in Core Workload #1260)

added bindings

• ElasticSearch 5 REST client ([elasticsearch5-rest] add forgotten elasticsearch5-rest binding. #1231)
• Azure Cosmos DB (Azure Cosmos [DB] #1264 Optimizing the driver and fixing update #1298 Updating to the latest driver and removing flag that are no longer needed. #1300)
• Postgres NoSQL ([PostgreNoSQL] Added NoSQL support for PostgreSQL. #1242)
• Apache Crail (incubating) (Added support for Apache Crail (Incubating) #1266)
• Table Store from Alibaba Cloud ([tablestore] Add binding for Alibaba Cloud's TableStore #1286)
• Toshiba GridDB ([griddb] GridDB binding #1258)

updated bindings

• Compat for MongoDB 4 ([mongodb] add compatibility for MongoDB 4.0 #1217)
• JDBC adds multi-row inserts ([jdbc] support JDBC option to rewrite batch statement to multi-row in… #1220)
• OrientDB updated to version 2.2.37 ([orientdb] fixed issue #1045, updated to orientdb version 2.2.37 #1256)
• memcached fixes a logic error where individual fields would not get checked ([Memcached] misbehavior when readallfields/writeallfields are false  #1153)
• Apache Cassandra can optionally use SSL to connect to the cluster (Adding the ability to connect to Cassandra using SSL connections. #1294)
• Apache HBase add documentation for using client side buffering ([hbase098] document the client side buffering config. #1283)
• Apache Ignite version upgraded (Apache Ignite version updated #1270)
• Google Cloud Bigtable client upgraded ([cloudspanner bigtable] update client library versions #1293)
• Cloud Spanner client upgraded ([cloudspanner bigtable] update client library versions #1293)
• AsyncHBase client upgrade ([asynchbase] update to 1.8.2 #1255)

removed bindings

• Azure Document DB has been removed (Removing deprecated driver. #1295)

[busbey]

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

As a reminder, testing a given binding should at a minimum run through a load and a run phase. Ideally, one should go through the recommended sequence of workload steps from the "Running the workloads" section of the Core Workloads documentation.

[busbey]

I confirmed that the change to limit the thread count works. and I checked an HDP 2.6.5 HBase cluster with the hbase098, hbase10, hbase12, hbase14, and aysnchbase bindings.

[busbey]

I confirmed that the hbase20 binding works with a CDH6 HBase cluster.

[busbey]

oh and I confirmed that the fieldnameprefix stuff works.

[busbey]

Things that it'd be nice to test prior to marking the release as done, so that they don't need to be marked as experimental:

• @srmadscience mind checking that the voltdb stuff works in the release candidate?
• @KowsarAtz can you verify SQL Server with the JDBC binding?
• @seybi87 would you mind checking autofailover with the JDBC binding?
• @dfquaresma could you check elasticsearch5-rest?
• @voellm can you check Azure CosmosDB and Cassandra with SSL?
• @leschekhomann can you check Postgres NoSQL?
• @patrickstuedi can you check Apache Crail?
• @HoboChen can you check Alibaba Tablestore?
• @knonomura can you check GridDB?
• @stutiredboy or @allanbank could you check on mongodb 4.0?
• @FloBWer can you check on OrientDB?
• @calin-iorgulescu or @rizlik could you check on memcached?
• @isuntsov-gridgain would you mind checking Apache Ignite?
• @flint-dominic can you check cloud spanner and bigtable?

[voellm]

We regularly build and test both the Azure CosmoDB and Cassandra + SSL changes and they work as expected. What kind of update / test output / etc would you like?

[busbey]

We regularly build and test both the Azure CosmoDB and Cassandra + SSL changes and they work as expected. What kind of update / test output / etc would you like?

Doing those same checks for the 0.17.0 RC tag specifically would be great. Generally we take folks who test at their word rather than requiring a copy of any results.

[KowsarAtz]

Yes! I've run the tests on MSSQL multiple times (with different jdbc drivers) and it works fine.

…

On Mon, Sep 23, 2019 at 6:50 PM Sean Busbey ***@***.***> wrote: Things that it'd be nice to test prior to marking the release as done, so that they don't need to be marked as experimental: - @srmadscience <https://github.com/srmadscience> mind checking that the voltdb stuff works in the release candidate? - @KowsarAtz <https://github.com/KowsarAtz> can you verify SQL Server with the JDBC binding? - @seybi87 <https://github.com/seybi87> would you mind checking autofailover with the JDBC binding? - @dfquaresma <https://github.com/dfquaresma> could you check elasticsearch5-rest? - @voellm <https://github.com/voellm> can you check Azure CosmosDB and Cassandra with SSL? - @leschekhomann <https://github.com/leschekhomann> can you check Postgres NoSQL? - @patrickstuedi <https://github.com/patrickstuedi> can you check Apache Crail? - @HoboChen <https://github.com/HoboChen> can you check Alibaba Tablestore? - @knonomura <https://github.com/knonomura> can you check GridDB? - @stutiredboy <https://github.com/stutiredboy> or @allanbank <https://github.com/allanbank> could you check on mongodb 4.0? - @FloBWer <https://github.com/FloBWer> can you check on OrientDB? - @calin-iorgulescu <https://github.com/calin-iorgulescu> or @rizlik <https://github.com/rizlik> could you check on memcached? - @isuntsov-gridgain <https://github.com/isuntsov-gridgain> would you mind checking Apache Ignite? - @flint-dominic <https://github.com/flint-dominic> can you check cloud spanner and bigtable? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1355?email_source=notifications&email_token=ALWKENV6LUB2DUCUJY5BER3QLDNFTA5CNFSM4IY47ZRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7LHHUY#issuecomment-534148051>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALWKENXYUXDL4UH7QUCJGPLQLDNFTANCNFSM4IY47ZRA> .

[srmadscience]

"@srmadscience mind checking that the voltdb stuff works in the release candidate?".

Done for VoltDB v9.1.1.

Question: Any idea when this is 'officially' released?

[busbey]

Question: Any idea when this is 'officially' released?

I'll wait a couple of days to make sure no one else is testing any of the outstanding stuff. Then I'll post a release and link it here. This issue will be closed once download links, etc get updated.

[patrickstuedi]

Done. Ran the basic tests for Crail against the 0.17.0 RC and things work fine.

[leschekhomann]

@busbey: At the moment I am busy, but I try to test the binding during the next week.

[knonomura]

@busbey
Done for GridDB.
I can build and run successfully 0.17.0 RC tag.

[voellm]

I have built and run the Azure Cosmos [SQL] workloads and well as testing connections to Azure Cosmos Cassandra using the useSSL flag.

[allanbank]

Ran my test script for MongoDB versions:

• 4.2.0
• 4.0.12
• 3.6.14
• 3.4.23
• 3.2.22
• 3.0.15
• 2.6.12

No issues.

[rizlik]

I can test this in the beginning of the next week.
btw as far as I'm understanding just one of the issue is addressed. As the main one remains unsolved isn't better to re-open the issue (#1153 )?
Also does the, now fixed, data integrity triggers an error without fixing the wrong update logic?

[busbey]

I can test this in the beginning of the next week.
btw as far as I'm understanding just one of the issue is addressed. As the main one remains unsolved isn't better to re-open the issue (#1153 )?
Also does the, now fixed, data integrity triggers an error without fixing the wrong update logic?

I'd love someone to test and find out the answers to these questions. Either reopening or a new issue would be fine, if there's still problems.

[rizlik]

re memcahed:

e6bd739 looks ok but it doesn't fix the issues. In particular on an update operation all the fields but the updated one are destroyed and dataintegrity doesn't catch this. I think it would be better to open two new separated issues. I attach a raw simple script that show the wrong behavior (sorry for the wrong extension but github doesn't allow me to attach .sh).

If it looks sound to you I can open the issues and add some minor details.
memcached_test.sh.txt

[busbey]

Yep, your analysis looks correct. Open the two issues and link them here please? I'll list them as known issues for the release.

[rizlik]

Yep, your analysis looks correct. Open the two issues and link them here please? I'll list them as known issues for the release.

Here they are: #1358 and #1359

[seybi87]

run several load/run phase tests for with the following auto-failover JDBC connection string with the
PostgresSQL JDBC Driver against CockroachDB 2.0.3
jdbc:postgresql://IP1:PORT1, IP2:PORT2,IP3:PORT3/ycsb?sslmode=disable;jdbc:postgresql://IP1:PORT1, IP2:PORT2,IP3:PORT3/ycsb?sslmode=disable

Execution works without any problems.

Applied the load phase in combination with a node failure to test the auto-failover explicitly:
One YCSB thread seems to be entering a non-recoverable error state and is not terminating but keeps on reporting 0 ops/s.
Yet, I did not have time to investigate further if this behavior is caused by CockroachDB or if there is an issues in the JDBC binding (it worked with the same delimiter changes applied to the former 0.12.0 YCSB version)

Anyways, the load/run phase execution works without issues if the newly enabled auto-failover capabilites are not used.

[isuntsov-gridgain]

I've checked Ignite client. It works. вт, 1 окт. 2019 г. в 13:30, seybi87 <[email protected]>:

…

run several load/run phase tests for with the following auto-failover JDBC connection string with the PostgresSQL JDBC Driver against CockroachDB 2.0.3 jdbc:postgresql://IP1:PORT1, IP2:PORT2,IP3:PORT3/ycsb?sslmode=disable;jdbc:postgresql://IP1:PORT1, IP2:PORT2,IP3:PORT3/ycsb?sslmode=disable Execution works without any problems. Applied the load phase in combination with a node failure to test the auto-failover explicitly: One YCSB thread seems to be entering a non-recoverable error state and is not terminating but keeps on reporting 0 ops/s. Yet, I did not have time to investigate further if this behavior is caused by CockroachDB or if there is an issues in the JDBC binding (it worked with the same delimiter changes applied to the former 0.12.0 YCSB version) Anyways, the load/run phase execution works without issues if the newly enabled auto-failover capabilites are not used. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1355?email_source=notifications&email_token=ACDWD36ERA4HDSBG7HUUIQLQMMRCZA5CNFSM4IY47ZRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAAZLZA#issuecomment-536974820>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACDWD33WLZW26ZA55SOMUPTQMMRCZANCNFSM4IY47ZRA> .

-- Best Regards, Ilya Suntsov email: [email protected] *GridGain Systems* www.gridgain.com

[busbey]

I'm going to add #1356 as a known issue and wrap up this release in the next day or so.

[busbey]

the release is up

I'm going to work through the steps for publishing to maven central (for core and binding-parent) before closing this issue out.

let me know if the release notes look like they're missing anything.

[leschekhomann]

Hi @busbey,
I tested the Postgres NoSQL binding against the official docker containers of PostgreSQL 9.5 and 9.6 from https://hub.docker.com/_/postgres. I run the sequence with the default parameters and workloads as described in "Running the workloads" without changing the number of threads or targets. At the moment the execution of the sequence only works when a property file is provided by the user since the URL, user name and user password are empty strings by default. Furthermore, an exception is thrown when the target database does not exist.

[busbey]

Thanks for the update! I'll move postgresnosql to the tested set in the release notes.

[HoboChen]

As I left alibaba cloud, @RaymondChina will take over the work you mentioned; thanks for your time! @busbey

[RaymondChina]

for Tablestore, the test pass. @busbey

what I have done :

1. clone the repo, switch to 0.17.0-RC1
2. follow the steps in YCSB/Tablestore/README.md, apply account, create instance, create table, fill configuration, start test cases
3. the result is ok

[busbey]

Thanks @RaymondChina! I updated the release notes.

Note to self: I still need to upload the convenience tarballs for postgrenosql and tablestore.

[busbey]

okay, I added convenience tarballs for postgrenosql and tablestore. also published the stuff needed to make a binding outside of the project on oss.sonatype.org.

Thanks everyone who helped out with testing!