封装的shinyproxy非常慢

Question

我使用堆栈: R、docker和shinyproxy部署了一个shinyapp，到目前为止，这些工具在用户满意的情况下非常棒。然而，我在负载平衡方面有点挣扎，以便在运行解决方案的更新时，我可以扩展和停止困扰用户。

在https://www.shinyproxy.io/shinyproxy-containers/的建议下，我完成了这个过程，但使用了集装箱码头引擎https://github.com/openanalytics/shinyproxy-config-examples/tree/master/02-containerized-docker-engine。当我运行java -jar shinyproxy-2.0.3.jar而不是容器时，我的解决方案运行得很好。但是现在当我将它装起来时，它会变得非常慢，事实上，即使在内部网络活跃的情况下，当我尝试打开容器时，容器也会被压碎。

目前，我只是在尝试测试容器shinyproxy是否可以工作而不给我带来问题，但最终失败了。

服务器上的Nginx配置

server {

        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;

        server_name qnumsolutions.com www.qnumsolutions.com;

        location / { 
       proxy_pass          http://127.0.0.1:8080/;

       proxy_http_version 1.1;
       proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection "upgrade";
       proxy_read_timeout 600s;

       proxy_redirect    off;
       proxy_set_header  Host             $http_host;
       proxy_set_header  X-Real-IP        $remote_addr;
       proxy_set_header  X-Forwarded-For  $proxy_add_x_forwarded_for;
       proxy_set_header  X-Forwarded-Protocol $scheme;
        }

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/qnumsolutions.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/qnumsolutions.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

Shinyproxy application.yml

proxy:
  title: The Operational Intelligence Solution
  logo-url: http://qnum.co.za/wp-content/uploads/2018/03/OI-Solution-Icon.png
  landing-page: /
  heartbeat-rate: 100000
  heartbeat-timeout: 600000
  port: 8080
  authentication: simple 
  container-log-path: ./container-logs
  admin-groups: admin
  usage-stats-url: http://159.65.95.235:8086/write?db=shinyproxy_usagestats
  # Example: 'simple' authentication configuration
  users:
  - name: info@qnum.co.za
    password: prupr1.
    groups: admin
  docker:
    url: http://localhost:2375
    port-range-start: 20000
  specs:
  - id: OISolution1
    description: Application is designed to help organisations use advanced analytics to manage product visibility and variance
    container-cmd: ["R", "-e shiny::runApp('/root/hostedoi')"]
    container-image: oisolution
    container-volumes: ["/home/shiny/database:/mnt/persistent1"]
    access-groups: admin
  - id: OISolution2
    description: Application is designed to help organisations use advanced analytics to manage product visibility and variance
    container-cmd: ["R", "-e shiny::runApp('/root/hostedoi1')"]
    container-image: oisolution1
    container-volumes: ["/home/shiny/database:/mnt/persistent1"]
    access-groups: admin

logging:
  file:
    shinyproxy.log

Dockerfile

FROM openjdk:8-jre

RUN mkdir -p /opt/shinyproxy/
RUN wget https://www.shinyproxy.io/downloads/shinyproxy-2.0.3.jar -O /opt/shinyproxy/shinyproxy.jar
COPY application.yml /opt/shinyproxy/application.yml

WORKDIR /opt/shinyproxy/
CMD ["java", "-jar", "/opt/shinyproxy/shinyproxy.jar"]

最后，sudo码头ps产量

CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS              PORTS                    NAMES
bc396c8bd26a        ois-shinyproxy      "java -jar /opt/shin…"   About a minute ago   Up About a minute   0.0.0.0:8080->8080/tcp   clever_beaver

我参考过的其他链接：https://fly.io/articles/load-balancing-a-fleet-of-docker-containers-using-fly/

您的协助将不胜感激。

Answer 1

您的usage-stats-url似乎有问题。也许防火墙或其他什么东西阻止ShinyProxy到达这个目的地？我可以复制这种缓慢的行为，但当我评论这句话时，它就消失了。

除此之外，你的application.yml中有一些关于码头的错误。我对它做了一些修改，并设法使用这种配置在本地计算机上运行它(nginx.conf和Dockerfile只是稍微修改了一下，以满足我对docker-compose的需求)：

proxy:
  title: The Operational Intelligence Solution
  logo-url: http://qnum.co.za/wp-content/uploads/2018/03/OI-Solution-Icon.png
  landing-page: /
  heartbeat-rate: 100000
  heartbeat-timeout: 600000
  port: 8080
  authentication: simple 
  container-log-path: ./container-logs
  admin-groups: admin
  #usage-stats-url: http://159.65.95.235:8086/write?db=shinyproxy_usagestats
  # Example: 'simple' authentication configuration
  users:
  - name: info@qnum.co.za
    password: prupre35A21.
    groups: admin
  docker:
    internal-networking: true
  specs:
  - id: 01_hello
    display-name: Hello Application
    description: Application which demonstrates the basics of a Shiny app
    container-cmd: ["R", "-e", "shinyproxy::run_01_hello()"]
    container-image: openanalytics/shinyproxy-demo
    container-volumes: ["/tmp:/mnt/persistent1"]
    container-network: shinyproxy_slow_default
    access-groups: admin
  - id: 06_tabsets
    container-cmd: ["R", "-e", "shinyproxy::run_06_tabsets()"]
    container-image: openanalytics/shinyproxy-demo
    container-volumes: ["/tmp:/mnt/persistent1"]
    container-network: shinyproxy_slow_default
    access-groups: admin

logging:
  file:
    shinyproxy.log

我使用docker-compose运行了所有内容，参见：

version: "3.1"

services:
  web:
    image: nginx:alpine
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./nginx.conf:/etc/nginx/conf.d/default.conf


  shinyproxy:
    image: sp_test
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./application.yml:/opt/shinyproxy/application.yml