What Can I Do If "context deadline exceed" Is Displayed During Chaincode Instantiation?
Symptom
The chaincode fails to be instantiated, and the following message is displayed: gRPC Transport Status Code: (4) DeadlineExceed. Description: context deadline exceed.
![Click to enlarge](https://support.huaweicloud.com/intl/en-us/bcs_faq/en-us_image_0000001353901472.png)
Possible Causes
Chaincode compilation consumes resources. Each peer takes up 200 MB memory to compile a Go chaincode and 500–600 MB memory to compile a Java chaincode. If your VM flavor is insufficient, for example, less than 4 vCPUs and 8 GB memory, the compilation may time out.
Solution
- Install and instantiate only one chaincode at a time.
- Upgrade the VM flavor.
- Instantiate the chaincode again. If the fault persists, contact technical support.
Chaincode Management FAQs
- How Do I Update a Chaincode If It Contains Bugs?
- How Do I View Chaincode Logs If My BCS Instance Uses Fabric v2.2?
- What Can I Do If Decompression Failed During Chaincode Installation?
- What Can I Do If "context deadline exceed" Is Displayed During Chaincode Instantiation?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore