What Can I Do If a BCS Instance Is in the Abnormal State?

Updated on 2023-03-07 GMT+08:00

View PDF

Symptom

The BCS instance is in the Abnormal state.

Fault Locating

Check item 1: Check whether the cluster, storage, and server resources on which the blockchain depends are normal.

Check item 2: Check whether the ECS specifications can meet the requirements.

Solution

Check item 1: Check whether the cluster, storage, and server resources on which the blockchain depends are normal.
1. Check the CCE cluster status.
  1. Log in to the CCE console, click Clusters, and check the status of the abnormal blockchain's cluster.
    If the cluster status is abnormal, locate the fault by following the CCE instructions: How Do I Rectify the Fault When the Cluster Status Is Unavailable?
  2. Log in to the CCE console, click Nodes, and check the status of the abnormal blockchain's nodes.
    If the node status is abnormal, locate the fault by following the CCE instructions: What Should I Do If a Cluster Is Available But Some Nodes Are Unavailable?
2. Check the ECS status.
  Log in to the ECS console and check the status of the ECS where the abnormal blockchain is deployed. ECS names usually take the following format: Name of the target blockchain's cluster-A random number.
  
  If the ECS is in the Stopped state, start the ECS, wait for about 5 minutes, and check its status again.
3. Check the storage status.
  1. Log in to the BCS console, go to the Instance Management page, and click the abnormal instance to view its volume type.
  2. Log in to the CCE console, click Clusters, and select a target cluster. On the cluster details page, click Storage. On the PersistentVolumeClaims (PVCs) tab page, check the storage status.
  3. If the SFS Turbo volume is in the Lost state, the state of the BCS instance will be displayed as Abnormal.
    Solution:
    
    Check whether the SFS Turbo file system exists or whether it is frozen, or contact the SFS technical support.

Check item 2: Check whether the ECS specifications can meet the requirements.
1. Log in to the ECS where the BCS instance is deployed.
  Log in to the ECS console, locate the target ECS, and click Remote Login in the Operation column. ECS names usually take the following format: Name of the target blockchain's cluster-A random number.
2. Run the top command to check whether the resource usage of any application is too high.
  Figure 1 top command details
  - If the CPU or memory usage of the peer, orderer, and baas-agent containers exceeds 60% and continues to increase as the transaction quantity increases, the current ECS specifications cannot meet the transaction requirements. In this case, you need to expand the ECS specifications.
  - If there are resources taking up 100% or even higher CPU or memory usage, contact technical support to remove unnecessary resources.

Parent topic: Abnormal Instance Statuses

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot