首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >使用超级分类账结构卡尺的资源监视器.错误:套接字挂起

使用超级分类账结构卡尺的资源监视器.错误:套接字挂起
EN

Stack Overflow用户
提问于 2021-02-17 04:21:32
回答 1查看 214关注 0票数 1

下面的配置用于使用超分类器卡尺 (0.4.2)监视位于远程计算机中的坞容器的资源利用率。

代码语言:javascript
复制
test:
    name: sample fabric network
    description: sample Network Benchmark
    workers:
      type: local
      number: 5
    rounds:
      - label: readAsset
        description: Using Chaincode Asset Management contract
        txNumber: 10000
        rateControl: 
          type: fixed-load
          opts:
            tps: 200
        workload:
          module: workload/readAsset.js
          arguments:
            contractId: asset-management
monitors:
  resource:
  - module: docker
    options:
      interval: 5
      containers:
         - http://34.233.177.187:7051/peer0.org1.example.com

它给出了Error retrieving remote containers: Error: socket hang up的错误,如下所示,并且不生成任何与资源监控相关的报告。尽管如此,事务还是使用卡尺提交到远程网络,我正试图从这里监控容器peer0.org1.example.com的资源利用情况。上面定义的机器IP和容器的名称在连接配置文件中定义.

从卡尺控制台登录

代码语言:javascript
复制
2021.02.17-03:46:22.319 info  [caliper] [worker-orchestrator]   5 workers prepared, progressing to test phase.
2021.02.17-03:46:22.945 error [caliper] [monitor-docker]    Error retrieving remote containers: Error: socket hang up
2021.02.17-03:46:22.947 info  [caliper] [round-orchestrator]    Monitors successfully started
2021.02.17-03:46:22.948 info  [caliper] [worker-message-handler]    Worker#0 is starting Round#0
2021.02.17-03:46:22.952 info  [caliper] [worker-message-handler]    Worker#1 is starting Round#0
2021.02.17-03:46:22.956 info  [caliper] [caliper-worker]    Worker #1 starting workload loop
2021.02.17-03:46:22.958 info  [caliper] [caliper-worker]    Worker #0 starting workload loop
2021.02.17-03:46:22.961 info  [caliper] [worker-message-handler]    Worker#2 is starting Round#0
2021.02.17-03:46:22.967 info  [caliper] [worker-message-handler]    Worker#3 is starting Round#0
2021.02.17-03:46:22.970 info  [caliper] [caliper-worker]    Worker #2 starting workload loop
2021.02.17-03:46:22.973 info  [caliper] [worker-message-handler]    Worker#4 is starting Round#0
2021.02.17-03:46:22.975 info  [caliper] [caliper-worker]    Worker #3 starting workload loop
2021.02.17-03:46:22.977 info  [caliper] [caliper-worker]    Worker #4 starting workload loop
2021.02.17-03:46:27.352 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 15 Succ: 10 Fail:0 Unfinished:5
2021.02.17-03:46:32.322 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 45 Succ: 30 Fail:0 Unfinished:15
2021.02.17-03:46:37.322 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 70 Succ: 60 Fail:0 Unfinished:10
2021.02.17-03:46:42.323 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 89 Succ: 79 Fail:0 Unfinished:10
2021.02.17-03:46:47.323 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 111 Succ: 103 Fail:0 Unfinished:8
2021.02.17-03:46:52.323 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 128 Succ: 120 Fail:0 Unfinished:8
2021.02.17-03:46:57.323 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 153 Succ: 148 Fail:0 Unfinished:5
2021.02.17-03:47:02.323 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 173 Succ: 165 Fail:0 Unfinished:8
2021.02.17-03:47:07.324 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 194 Succ: 189 Fail:0 Unfinished:5
2021.02.17-03:47:12.324 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 214 Succ: 205 Fail:0 Unfinished:9
2021.02.17-03:47:17.325 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 233 Succ: 223 Fail:0 Unfinished:10
2021.02.17-03:47:22.325 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 252 Succ: 239 Fail:0 Unfinished:13
2021.02.17-03:47:27.325 info  [caliper] [default-observer]  [readAsset Round 0 Transaction Info] - Submitted: 269 Succ: 267 Fail:0 Unfinished:2
20

当使用本地机器进行监视时,它就可以工作了。为此,我使用了以下配置,并成功地将其用于本地坞容器。配置如下:

代码语言:javascript
复制
monitors:
  resource:
  - module: docker
    options:
      interval: 5
      containers:
        - all

是否还有更多的配置来监视卡尺中的远程容器资源利用情况?

谢谢!

EN

回答 1

Stack Overflow用户

发布于 2021-02-17 09:21:19

卡尺使用dockerode@3.1.0模块连接到容器(https://www.npmjs.com/package/dockerode)--套接字挂起将表示由于超时或类似的原因未能创建连接。

可供选择的有两种:

  1. 调试基于dockerode的连接--也许在这里增加卡尺中的日志级别会有帮助?使用dockerode@3.1.0制作一个小应用程序相对容易,以检查它是否有能力连接到已传递的容器URL --如果您能够连接,而且同一个URL在卡尺中不工作,那么就有一个bug需要修复
  2. 切换到一个基于Prometheus的监视器,它使用CAdvisor来监视容器统计数据(您也可以在这里免费获得Grafana )。
票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/66235723

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档