search

hyperledger / caliper

A blockchain benchmark framework to measure performance of multiple blockchain solutions https://wiki.hyperledger.org/display/caliper
https://hyperledger.github.io/caliper/
Apache License 2.0
650 stars 402 forks source link

instantiate proposal was bad: Error: REQUEST_TIMEOUT #306

Closed CoreyLin closed 5 years ago

CoreyLin commented 5 years ago

Context

Env: 2 orgs, each org has 2 peers

Steps: Execute command "node benchmark/simple/main.js -n /home/yzapps/hyperledger/yingzi/caliper/network/fabric-v1.4-yingzi/2org2peercouchdb/fabric-node.json" note:1.omit "-c" parameter, which means using the default "config-linear-rate.yaml" as the benchmark config file 2.The content of used fabric-node.json is as following: fabric-node.zip

Expected Behavior

The benchmark test ran successfully and report was generated normally.

Actual Behavior

"instantiate proposal was bad: Error: REQUEST_TIMEOUT" error happened. The detailed log is attached: benchmark_log.zip

Could you please help me figure out what is wrong here? Thank you.

CoreyLin commented 5 years ago

@houqinghui qinghui, could you help? Thanks.

CoreyLin commented 5 years ago

I noticed that even though the benchmark test failed, "marbles" chaincode was actually successfully instantiated in the peer: 67cd54b00b2e65d533b5a6b425e2c8e

So I am curious that why the error log also shows "warn: [e2eUtils.js]: instantiate proposal was bad: Error: REQUEST_TIMEOUT"?

Besides, I noticed that in default "config-linear-rate.yaml", actually two chaincodes are configured: 1.marbles 2.simple So I wonder whether the error log means that "simple" chaincode was not successfully instantiated?

CoreyLin commented 5 years ago

And I checked the docker container. Both "marbles" and "simple" chaincodes' containers are started and running: bdafe153df599c442c3faa4961008bf Does docker container running means the instantiation of chaincodes is successful? Thanks.

CoreyLin commented 5 years ago

After I remove "simple" chaincode from network config file, the issue disappeared. It seems that the instantiation of "marbles" chaincode was successful. But another error happened. And I will create another issue to track the new error. I will close this issue now.