-
Notifications
You must be signed in to change notification settings - Fork 139
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
Error: No JSON object could be decoded #66
Comments
Does it work against an actual MongoDB cluster? It seems the error is that no tests actually ran. |
It is important to note that mongo-perf was designed to be run against MongoDB... not DocumentDB. We have a test harness over here... That harness was written to test real MongoDB as well as other flavors of document database that claim MongoDB compatibility. If you need more information about the differences between MongoDB and AWS DocumentDB I highly recommend this article. |
I receive the same error when pointing to a mongos. When I run the script against a single mongo instance it's working fine. |
Off the top of my head I can't think of a reason why it wouldn't work against a mongos too, but it is actually true that we only use these tests to test standalone instances. These tests are microbenchmarks and don't really represent realistic application workloads at all. I really recommend you follow the link provided by @mrlynn instead. |
i have similar error when running against mongo arbiter with 4 node mongodb replicaset. FYI i'm bale to connect to it using pymongo and write to it. |
This issue is repro for me as well against mongod.exe. |
Hi,
I'm aiming to use the benchmark tool to benchmark DocumentDB the Aws MongoDB database compatible.
I have followed the installation steps but I'm having issues running benchmarks
Environment setting
Running the benchmark script
The script is able to connect to the server, but it finishes the test without any output.
Am I missing something?
The text was updated successfully, but these errors were encountered: