Hyperledger Fabric Nodejs SDK Eventhub已关闭

问题描述 投票:2回答:2

我已经在IBM Blockchain平台上部署了示例fabcar网络,并使用此repository中的代码与之交互。当我单独调用每个函数时,交互很有效。

当我开发节点服务器并公开调用链代码的API时,就会出现问题。一旦我这样做,我开始得到错误

无法成功调用::错误:eventhub出现问题::错误:EventHub已关闭

奇怪的是,当我同时向POST调用发送3个请求时,我收到此错误。但是记录会插入到IBM云上。

当我同时发送100个请求时,只有大约20个请求插入云中,其余的显示此错误以及此类附加错误

错误:[Orderer.js]:sendBroadcast - 出错:“错误:14 UNAVAILABLE:连接失败\ n在createStatusError(/ home / trs-laptop-20 / Downloads / fabcar-network / node_modules / fabric-client / node_modules / grpc ClientDuplexStream._emitStatusIfDone上的/src/client.js:64:15)h。(/ home / trs -laptop-20 / Downloads / fab-network / node_modules :19)\ n在readCallback的ClientDuplexStream._readsDone(/home/trs-laptop-20/Downloads/fabcar-network/node_modules/fabric-client/node_modules/grpc/src/client.js:236:8)n中/home/trs-laptop-20/Downloads/fabcar-network/node_modules/fabric-client/node_modules/grpc/src/client.js:296:12)”

而且在某些情况下

错误:[client-utils.js]:sendPeersProposal - Promise被拒绝:错误:14 UNAVAILABLE:Connect new new new createStatusError(/ home / trs-laptop-20 / Downloads / fabcar-network / node_modules / fabric-client / node_modules / grpc / src / client.js:64:15)athome/trs-laptop-20/Downloads/fabcar-network/node_modules/fabric-client/node_modules/grpc/src/client.js:583:15

我无法理解为什么会出现这些错误。我必须开发一个可以处理负载的高性能应用程序,任何帮助和指导都会非常感激。

这是我的app.js代码:

'use strict';

//get libraries
const express = require('express');
const bodyParser = require('body-parser');
const request = require('request');
const path = require('path');

//create express web-app
const app = express();
const router = express.Router();
app.use(bodyParser.json());
const invoke = require('./invokeNetwork.js');

//declare port
var port = process.env.PORT || 8000;
if (process.env.VCAP_APPLICATION) {
  port = process.env.PORT;
}

//run app on port
app.listen(port, function() {
  console.log('app running on port: %d', port);
});

app.post('/api/post', async function(req,res){
    var carID = req.body.carID;
    var make = req.body.make;
    var model = req.body.model;
    var color = req.body.color;
    var owner = req.body.owner;

  await invoke.invokeCreate(carID, make, model, color, owner).then((response) => {
    //return error if error in response
    if (response.status == 500) {
      res.status(500).send({ error: response.message });
    } else {
      //else return success
      res.status(200).send({ message: response.message });
    }
  }).catch(err => {
    console.log(err);
  });

});

这是invokeNetwork.js代码

'use strict';

var Fabric_Client = require('fabric-client');
var path = require('path');
var util = require('util');
var os = require('os');
var fs = require('fs');

var isError = false;
var throwError = "";

//make sure we have the profiles we need
var networkConfig = path.join(__dirname, './config/network-profile.json')
var clientConfig = path.join(__dirname, './config/client-profile.json');

module.exports = {

invokeCreate: async function(carID, make, model, color, owner) {

  isError = false;

//try {

  checkProfilesExist(networkConfig, clientConfig); //terminates early if they are not found

// load the base network profile
var fabric_client = Fabric_Client.loadFromConfig(path.join(__dirname, './config/network-profile.json'));

// overlay the client profile over the network profile
fabric_client.loadFromConfig(path.join(__dirname, './config/client-profile.json'));

// setup the fabric network - get the channel that was loaded from the network profile
var channel = fabric_client.getChannel('defaultchannel');
var tx_id = null;

//load the user who is going to unteract with the network
fabric_client.initCredentialStores().then(() => {
  // get the enrolled user from persistence, this user will sign all requests
  return fabric_client.getUserContext('user1', true);
}).then((user_from_store) => {
  if (user_from_store && user_from_store.isEnrolled()) {
    console.log('Successfully loaded user1 from persistence');

  } else {
    throw new Error('Failed to get user1.... run registerUserNetwork.js');
  }

  // get a transaction id object based on the current user assigned to fabric client
  tx_id = fabric_client.newTransactionID();
  console.log("Assigning transaction_id: ", tx_id._transaction_id);

  // createCar chaincode function - requires 5 args, ex: args: ['CAR11', 'Honda', 'Accord', 'Black', 'Dave'],
  // changeCarOwner chaincode function - requires 2 args , ex: args: ['CAR11', 'MGK'],
    var request = {
        chaincodeId: 'fabcar',
        fcn: 'createCar',
        args: [carID, make, model, color, owner],
        txId: tx_id
  };

  // send the transaction proposal to the endorsing peers
  return channel.sendTransactionProposal(request);
}).then((results) => {
  var proposalResponses = results[0];
  var proposal = results[1];
  let isProposalGood = false;
  if (proposalResponses && proposalResponses[0].response &&
    proposalResponses[0].response.status === 200) {
    isProposalGood = true;
    console.log('Transaction proposal was good');
  } else {
    console.error('Transaction proposal was bad');

  }
  if (isProposalGood) {
    console.log(util.format(
      'Successfully sent Proposal and received ProposalResponse: Status - %s, message - "%s"',
      proposalResponses[0].response.status, proposalResponses[0].response.message));

    // build up the request for the orderer to have the transaction committed
    var request = {
      proposalResponses: proposalResponses,
      proposal: proposal
    };

    // set the transaction listener and set a timeout of 30 sec
    // if the transaction did not get committed within the timeout period,
    // report a TIMEOUT status
    var transaction_id_string = tx_id.getTransactionID(); //Get the transaction ID string to be used by the event processing
    var promises = [];

    var sendPromise = channel.sendTransaction(request);
    promises.push(sendPromise); //we want the send transaction first, so that we know where to check status

    // get an eventhub once the fabric client has a user assigned. The user
    // is required bacause the event registration must be signed
    console.error('Getting event hub');
    let event_hub = fabric_client.getEventHub('org1-peer1');

    // using resolve the promise so that result status may be processed
    // under the then clause rather than having the catch clause process
    // the status
    let txPromise = new Promise((resolve, reject) => {
      let handle = setTimeout(() => {
        event_hub.disconnect();
        resolve({ event_status: 'TIMEOUT' }); //we could use reject(new Error('Trnasaction did not complete within 30 seconds'));
      }, 3000);
      event_hub.connect();
      event_hub.registerTxEvent(transaction_id_string, (tx, code) => {
        // this is the callback for transaction event status
        // first some clean up of event listener
        clearTimeout(handle);
        event_hub.unregisterTxEvent(transaction_id_string);
        event_hub.disconnect();

        // now let the application know what happened
        var return_status = { event_status: code, tx_id: transaction_id_string };
        if (code !== 'VALID') {
          console.error('The transaction was invalid, code = ' + code);
          resolve(return_status); // we could use reject(new Error('Problem with the tranaction, event status ::'+code));
        } else {
          console.log('The transaction has been committed on peer ' + event_hub._ep._endpoint.addr);
          resolve(return_status);
        }
      }, (err) => {
        //this is the callback if something goes wrong with the event registration or processing
        reject(new Error('There was a problem with the eventhub ::' + err));
        throwError += err;
      });
    });
    promises.push(txPromise);

    return Promise.all(promises);
  } else {
    console.error('Failed to send Proposal or receive valid response. Response null or status is not 200. exiting...');
    throw new Error('Failed to send Proposal or receive valid response. Response null or status is not 200. exiting...');
  }
}).then((results) => {
  console.log('Send transaction promise and event listener promise have completed');
  // check the results in the order the promises were added to the promise all list
  if (results && results[0] && results[0].status === 'SUCCESS') {
    console.log('Successfully sent transaction to the orderer.');
  } else {
    console.error('Failed to order the transaction. Error code: ' + response.status);
    throw new exception("Transaction");
  }

  if (results && results[1] && results[1].event_status === 'VALID') {
    console.log('Successfully committed the change to the ledger by the peer');
    return true;
  } else {
    console.log('Transaction failed to be committed to the ledger due to ::' + results[1].event_status);
  }
}).catch((err) => {
  console.error('Failed to invoke successfully :: ' + err);
  isError = true;
  throwError += err;
});

console.log(isError);

return {
  message: (isError) ? throwError : 'Success Transaction'
}

function checkProfilesExist(networkConfig, clientConfig) {
  if (!fs.existsSync(networkConfig)) {
    console.log("Error: config file 'network-profile.json' not found.");
    console.log("Make sure 'network-profile.json' is copied into the './config' folder.");
    process.exit()
  }

  //make sure we have the client profile we need

  if (!fs.existsSync(clientConfig)) {
    console.log("Error: config file 'client-profile.json' not found.");
    console.log("Make sure 'client-profile.json' is copied into the './config' folder.");
    process.exit()
  }
}

}

}
//throw new exception("Exceoption thrown");
//return true;
// }
//   catch(err) {
//     //print and return error
//     console.log(err);
//     var error = {};
//     error.error = err.message;
//     return error;
//     }
//   }
// }
node.js hyperledger-fabric hyperledger
2个回答
3
投票

所以,我们一直在玩织物,试图测试一些性能。我遇到了你所处理的所有问题,所以我们会解释我们的问题,希望他们会帮助你。

Eventhub关闭

Error: There was a problem with the eventhub ::Error: EventHub has been shutdown

Problem

注意到这会在我们发送大量交易时出现,并且当我们使用狡猾的互联网连接时也会出现。 fabric docs state

事件是短暂的,因此如果注册的侦听器在事件发布时崩溃,则侦听器将错过事件

我相信问题是eventhub试图连接到我们的API,但是连接存在问题。这会导致eventhub超时(因为它没有收到响应),然后导致eventhub关闭。

Solution

Fabric架构文档再次推荐:

  • 在块级别上进行监听,因此即使您错过了一个块,也可以获取旧块(上面的Fabric文档链接中的更多信息)
  • 建立自己的队列

看看这个pastebin是否有基本的块监听器 - > https://pastebin.com/wCd6Ni46

错误:14无法使用

Problem

我们注意到当我们开始发送大量交易时,我们最终会得到一个错误:14 UNAVAILABLE,但这是在真正充斥着大量交易的网络之后。我认为我们可以批量购买20个,但是当我们快速连续发送50个或更多时,它无法处理它。

记住块,至少在IBP启动器添加上,限制为一个块的10次转换,因此它需要等待它被开采才能处理下一组事务。在这个过程中,我相信缓冲区已经填满,然后你不能发送太多。

因此,您的两个错误是订货人被淹没或同行被太多交易淹没。

Solution

将事务批处理为块,并等待这些事务确认后再发送更多事务。这为您的同龄人和订货人提供了一些呼吸空间。

希望这有帮助!


0
投票

正如Priyav Shah非常清楚地解释的那样,完整的修复程序要求您修改API以解决问题。

如果您只是寻找一个短期解决方案来重新启动对等体上的eventhub监听器,一个简单的解决方法是重新启动对等体并使其重新加入通道并在其上重新安装链接代码。

© www.soinside.com 2019 - 2024. All rights reserved.