-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.10.0 #772
Comments
Changes since 0.9.0:
#737 is going to require updates to our docs before final release. it looks like we'll need to retest a minimum of the following: MySQL (via JDBC), mongo, mongo-async, cassandra2. I'd like to get rados tested since it's new. Anything else folks would like to see? |
I'm not sure how I missed this in reviewing #737, but I now notice that the python script for running ycsb is still in place. Should we leave this in parallel with the dedicated scripts for this release? I wouldn't want to keep it around much longer than that. |
RC1 is up, if folks want to start testing: https://github.com/brianfrankcooper/YCSB/releases/tag/0.10.0-RC1
Any volunteers for checking that the cassandra2 module works? I'll get things tested on windows (both with the python wrapper and the new batch script). |
FWIW, I tried jdbc-binding with PostgreSQL 9.5.2 and its JDBC4 Driver. All workloads succeeded with db.batchsize=100 :) https://gist.github.com/sekikn/cc6c7d034bc3343253df7061c75fb1bb |
I am testing the Cassandra2 module in 0.10.0RC1 and will update about it here. |
I'll runs some tests on the scripts. I'd appreciate it if everyone running tests would also try out the new scripts and report any issues. Please try out "ycsb.sh" instead of "ycsb", or "ycsb.bat" for Windows systems. I wasn't sure weather to leave the python script there either. I agree, though, probably should not keep it around too long if we plan to switch to the platform scripts. |
I created pull request #777 to address issues I found when testing on Windows. It would be good to include for this release. |
I am getting this when I run YCSB on Cassandra 2.1.0
I think its a maven error, I do not use/know maven so maybe somebody else can test this. |
I am sorry for the delayed reply. On Wed, Jun 22, 2016 at 2:01 PM Sean Busbey notifications@github.com
CPS Lab. (Cyber-Physical Systems Laboratory in Hanyang University) |
@engineerakki The release candidate is a source code release. Try to do a maven build first. You can check that you have maven v3 installed with "mvn -v". Then build with "mvn clean package". |
Okay, @cmatser I've got your change from #777 on the staging branch. I'll cut a new RC later today and then go through my windows tests. @engineerakki if you need more help with Cassandra2, please let us know. If anyone can take care of mongo or mysql, let me know. |
@busbey , I can run tests on mysql. |
Tested MySQL 5.5 on ubuntu with JDBC binding. All good. |
found #784, new script files not found in binary tarball. |
on the plus side, the new batch file appears to solve #335. |
@busbey as mentioned on the other thread if we can cherry pick 44660de and 5edb1d9 that would be great, and yes it requires 2.3.1 which is set on master (https://github.com/brianfrankcooper/YCSB/blob/master/pom.xml#L95) |
@busbey yes! thanks much - once merged in I can do the testing. |
Release Candidate 3 is ready, should include the fix for the new scripts and the couchbase changes: https://github.com/brianfrankcooper/YCSB/releases/tag/0.10.0-RC3 |
looks like testing to go:
I'd like to cut the release tomorrow evening. |
anyone have a copy of the script @allanbank uses to test mongodb? @engineerakki you going to be able to get to the cassandra2 testing still? |
Draft release notes, with cassandra, couchbase, and mongodb moved into the "untested" category. https://gist.github.com/busbey/0cb1bf8ad36fc9e4bbb0e2fe1f3b7507 |
Sorry that I am slow to the party. I started the script last night but forgot to set Java to 1.7 for the build to work. I am re-running now with the script now and will let you know the results. It takes a couple of hours to run. |
Sweet! Any chance of publishing the script so that others can share the task next time? |
Just put up a gist. No complaining about my bash skills. https://gist.github.com/allanbank/3c89da1868bb25a16fdafb1786585af8 You can just copy it into an empty directory and run it from a shell and it will pull down everything from the internet:
I run a grep after the tests to check for errors from the same directory.
I need to get a new computer because the script has only gotten through these MongoDB versions" 3.2.7, 3.0.12 and part of 2.6.12. No issues so far and I think that is good enough for the release. |
All of the MongoDB versions finished and look good. Versions tested:
For the release notes I would change the note for MongoDB from:
to
'NONE' is the current/prefered name for 'w:0'. Other than that the release notes look good to me. |
Sorry for the delay on Couchbase, been traveling andd will complete testing on Monday! |
testing done, found and fixed some regressions recently introduced, please see #789 |
Also, what couchbase version number should I record as having been tested? |
Thanks @allanbank! the script is great and I kind of want to start making something like that for all the bindings. |
@busbey no need for an extra RC for me. Tested with 4.5 and 4.0. |
okay, release notes updated for the couchbase2 fix, and the testing for couchbase and mongodb: https://gist.github.com/busbey/0cb1bf8ad36fc9e4bbb0e2fe1f3b7507 I won't be able to grab my signing machine until later this evening, but I'll start making the release artifacts now. If someone needs something to make it in to 0.10.0 still, speak up soon. |
release is up! https://github.com/brianfrankcooper/YCSB/releases/tag/0.10.0 I'll start sending out announcement emails this evening. |
README update: #792 |
anyone know if Rados has a user forum where I can announce the release? |
I think we're past the reasonable window for announcing this release. I'm giving up on it. Let's just make sure the 0.11.0 release is really good. :) |
Hi Folks!
I'm going to spin a release candidate shortly. If there's an in-progress PR that's close that you'd like to see included please try to get it in soon.
I'll comment with the current set of issues later this evening.
The text was updated successfully, but these errors were encountered: