[READ-FAILED] and [UPDATE-FAILED], When using YCSB for MongoDB Benachmarking

[morcelicaio]

Hi All.

I'm trying to run the benchmark with MongoDB through netbeans, but I'm getting the error of [READ-FAILED] and [UPDATE-FAILED].

I did several tests and I can't find the solution to do a clean run. Could anyone help? I'm using a 3.6.3 version of maven and Java 8.

To try to execute it by calling the AsyncMongoDbClient class I imported the MongoDB dependencies (allanbank) and copied the classes (AsyncMongoDbClient.java, MongoDbClient.java and OptionsSupport.java) from the MongoDB Binding project into the YCSB Core project.

This is the output log

cd C:\YCSB-master\core; "JAVA_HOME=C:\Program Files\Java\jdk1.8.0_221" cmd /c """C:\Program Files (x86)\NetBeans\netbeans\java\maven\bin\mvn.cmd" -Dexec.args="-classpath %classpath site.ycsb.Client -db site.ycsb.AsyncMongoDbClient -s -p mongodb.url=mongodb://127.0.0.1:27017/ycsb?w=1y&journal=true -P C:\YCSB-master\core\src\main\java\site\ycsb\workloads\workloada.properties" -Dexec.executable="C:\Program Files\Java\jdk1.8.0_221\bin\java.exe" -Dmaven.ext.class.path="C:\Program Files (x86)\NetBeans\netbeans\java\maven-nblib\netbeans-eventspy.jar" -Dfile.encoding=UTF-8 org.codehaus.mojo:exec-maven-plugin:1.5.0:exec"" Running NetBeans Compile On Save execution. Phase execution is skipped and output directories of dependency projects (with Compile on Save turned on) will be used instead of their jar artifacts. Scanning for projects...

Building Core YCSB 0.18.0-SNAPSHOT --- exec-maven-plugin:1.5.0:exec (default-cli) @ core --- Command line: -db site.ycsb.AsyncMongoDbClient -s -p mongodb.url=mongodb://127.0.0.1:27017/ycsb?w=1y&journal=true -P C:\YCSB-master\core\src\main\java\site\ycsb\workloads\workloada.properties YCSB Client 0.18.0-SNAPSHOT

Loading workload... Starting test. 2022-03-29 11:26:27:050 0 sec: 0 operations; est completion in 0 second mongo connection created with mongodb://127.0.0.1:27017/ycsb?w=1y&journal=true DBWrapper: report latency for each error is false and specific error codes to track for latency are: [] 2022-03-29 11:26:28:199 1 sec: 1000 operations; 853,24 current ops/sec; [UPDATE-FAILED: Count=516, Max=858623, Min=195, Avg=1946,45, 90=348, 99=750, 99.9=2179, 99.99=858623] [READ: Count=0, Max=0, Min=9223372036854775807, Avg=?, 90=0, 99=0, 99.9=0, 99.99=0] [CLEANUP: Count=1, Max=1575, Min=1575, Avg=1575, 90=1575, 99=1575, 99.9=1575, 99.99=1575] [UPDATE: Count=0, Max=0, Min=9223372036854775807, Avg=?, 90=0, 99=0, 99.9=0, 99.99=0] [READ-FAILED: Count=484, Max=6587, Min=95, Avg=155,82, 90=170, 99=372, 99.9=6587, 99.99=6587] [OVERALL], RunTime(ms), 1172 [OVERALL], Throughput(ops/sec), 853.2423208191126 [TOTAL_GCS_PS_Scavenge], Count, 0 [TOTAL_GC_TIME_PS_Scavenge], Time(ms), 0 [TOTAL_GCTIME%PS_Scavenge], Time(%), 0.0 [TOTAL_GCS_PS_MarkSweep], Count, 0 [TOTAL_GC_TIME_PS_MarkSweep], Time(ms), 0 [TOTAL_GC_TIME%PS_MarkSweep], Time(%), 0.0 [TOTAL_GCs], Count, 0 [TOTAL_GC_TIME], Time(ms), 0 [TOTAL_GC_TIME%], Time(%), 0.0 [UPDATE-FAILED], Operations, 516 [UPDATE-FAILED], AverageLatency(us), 1946.4457364341085 [UPDATE-FAILED], MinLatency(us), 195 [UPDATE-FAILED], MaxLatency(us), 858623 [UPDATE-FAILED], 95thPercentileLatency(us), 428 [UPDATE-FAILED], 99thPercentileLatency(us), 750 [READ], Operations, 0 [READ], AverageLatency(us), NaN [READ], MinLatency(us), 9223372036854775807 [READ], MaxLatency(us), 0 [READ], 95thPercentileLatency(us), 0 [READ], 99thPercentileLatency(us), 0 [READ], Return=NOT_FOUND, 484 [CLEANUP], Operations, 1 [CLEANUP], AverageLatency(us), 1575.0 [CLEANUP], MinLatency(us), 1575 [CLEANUP], MaxLatency(us), 1575 [CLEANUP], 95thPercentileLatency(us), 1575 [CLEANUP], 99thPercentileLatency(us), 1575 [UPDATE], Operations, 0 [UPDATE], AverageLatency(us), NaN [UPDATE], MinLatency(us), 9223372036854775807 [UPDATE], MaxLatency(us), 0 [UPDATE], 95thPercentileLatency(us), 0 [UPDATE], 99thPercentileLatency(us), 0 [UPDATE], Return=NOT_FOUND, 516 [READ-FAILED], Operations, 484 [READ-FAILED], AverageLatency(us), 155.81611570247935 [READ-FAILED], MinLatency(us), 95 [READ-FAILED], MaxLatency(us), 6587 [READ-FAILED], 95thPercentileLatency(us), 205 [READ-FAILED], 99thPercentileLatency(us), 372 BUILD SUCCESS Total time: 2.375 s Finished at: 2022-03-29T11:26:28-03:00 Final Memory: 9M/245M

[busbey]

that output looks like you didn't have a successful load prior to starting the run.

[morcelicaio]

Thank you @busbey . In fact, it had to be loaded beforehand. I redid the tests and was successful.