5

I have deployed the Hyperledger fabric on AWS using cello ansible with dockers. Everything works fine. I was able to do a transaction using composer playground. In a process for vertical scale-up the system, I have created a bigger AWS instance using old AMI. I have correct all the dns, docker and flannel settings. Updated /etc/hosts files on both the VMs. Brought all the docker container up and running. Now when I try to do a transaction, I am getting below error by composer-playground:

Error: Error trying invoke business network. Error: Failed to send peer responses for transaction '02be502e532dfe5c153fa2fc5ecbb599a387834e32f4eb5b1806949335cfcd26' to orderer. Response status 'SERVICE_UNAVAILABLE'

I have checked all the docker logs(i.e. orderer, peer, kafka, zookeeper) could not able to find exact error.

Can anyone please tell me what I am missing here?

Thanks.

Gaurang Singh
  • 188
  • 9
  • By the way, I was able to scale up the fabric network with below steps: 1) Stop the AWS instance 2) Change the type of AWS instance 3) Start the AWS instance and bring up all the docker container. – Gaurang Singh Dec 18 '18 at 11:13
  • Hey. I am face Response status 'SERVICE_UNAVAILABLE. Can have any solution for that – salman faris Aug 23 '19 at 09:10
  • @salmanfaris have you followed the process as I mentioned the comment? If yes then can you please let me know in which order you are bringing up docker services? – Gaurang Singh Aug 26 '19 at 12:26

2 Answers2

0

@Gaurang Singh

whenever a new transaction happened after endorsing happens client will send it to orderer.

SERVICE_UNAVAILABLE:

Which means orderer is not able to communicate with other orderers, kafka is not reachable.

Kafka ordering service has numerous connection problems.

Tip1: try to restart orderers one by one it will connect to kafka brokers and work properly

Tip2: use raft instead of kafka

Narendranath Reddy
  • 3,833
  • 3
  • 13
  • 32
0

I was able to scale up the fabric network with the following steps:

  1. Stop the AWS instance

  2. Change the type of AWS instance

  3. Start the AWS instance and bring up all the docker container.

Now bring up the service in this order: ca, zookeeper, kafka, orderer, couchDB, peers, client applications.

Wai Ha Lee
  • 8,598
  • 83
  • 57
  • 92
Gaurang Singh
  • 188
  • 9
  • Is the problem that the underlying resource of the server is too low? Do I need to scale the server up? – muyat Jan 08 '21 at 10:05