我正在Node.js中使用Socket.IO开发一个应用程序,这个应用程序是使用Docker部署的,我希望可以选择应用程序服务的多个实例。但是,当有多个实例时,应用程序就失败了。故障涉及浏览器中的错误,因为每个Socket.IO消息都有错误,应该在消息中发送的数据永远不会到达,等等。
Docker Stack文件有四个服务
在多节点application
connect-redis
SessionStore,并使用socket.io-redis
执行多节点Socket.IO f 211
在Socket.IO中,有一个例行的保持活动请求,例如/socket.io/?EIO=3&transport=polling&t=NLjcKJj&sid=X5UnuTjlYNJ4N8OsAAAH
上的GET。此请求可在反向代理的日志文件中看到,并由应用程序处理。Engine.IO的调试输出显示它接收到了这些请求。
具体地说:
2020-10-28T05:06:02.557Z Net read redis:6379 id 0
2020-10-28T05:06:02.557Z socket.io:socket socket connected - writing packet
2020-10-28T05:06:02.557Z socket.io:socket joining room X5UnuTjlYNJ4N8OsAAAH
2020-10-28T05:06:02.557Z socket.io:client writing packet {"type":0,"nsp":"/"}
2020-10-28T05:06:02.557Z socket.io:socket joined room [ 'X5UnuTjlYNJ4N8OsAAAH' ]
2020-10-28T05:06:02.656Z engine intercepting request for path "/socket.io/"
2020-10-28T05:06:02.656Z engine handling "GET" http request "/socket.io/?EIO=3&transport=polling&t=NLjcKJj&sid=X5UnuTjlYNJ4N8OsAAAH"
2020-10-28T05:06:02.656Z engine setting new request for existing client
2020-10-28T05:06:02.655Z engine intercepting request for path "/socket.io/"
2020-10-28T05:06:02.655Z engine handling "POST" http request "/socket.io/?EIO=3&transport=polling&t=NLjcKJh&sid=X5UnuTjlYNJ4N8OsAAAH"
2020-10-28T05:06:02.655Z engine unknown sid "X5UnuTjlYNJ4N8OsAAAH"
2020-10-28T05:06:02.774Z engine intercepting request for path "/socket.io/"
2020-10-28T05:06:02.774Z engine handling "GET" http request "/socket.io/?EIO=3&transport=polling&t=NLjcKLI&sid=X5UnuTjlYNJ4N8OsAAAH"
2020-10-28T05:06:02.774Z engine unknown sid "X5UnuTjlYNJ4N8OsAAAH"
2020-10-28T05:06:02.775Z engine intercepting request for path "/socket.io/"
2020-10-28T05:06:02.775Z engine handling "POST" http request "/socket.io/?EIO=3&transport=polling&t=NLjcKLJ&sid=X5UnuTjlYNJ4N8OsAAAH"
2020-10-28T05:06:02.775Z engine setting new request for existing client
2020-10-28T05:06:02.775Z socket.io:client client close with reason transport close
2020-10-28T05:06:02.775Z socket.io:socket closing socket - reason transport close
2020-10-28T05:09:14.955Z socket.io:client client close with reason ping timeout
2020-10-28T05:09:14.955Z socket.io:socket closing socket - reason ping timeout
日志上写着engine unknown sid "X5UnuTjlYNJ4N8OsAAAH"
的消息似乎很重要。它是说会话ID是未知的。但是会话在使用REDIS的节点之间共享。因此,不明白为什么会话将是未知的,因为它们应该使用connect-redis
共享。
另一件重要的事情是浏览器中的日志记录。
在JavaScript控制台中有以下消息的连续报告:
WebSocket connection to 'ws://DOMAIN-NAME/socket.io/?EIO=3&transport=websocket&sid=h2aFFkOvNZtFc1DcAAAI' failed: WebSocket is closed before the connection is established.
Failed to load resource: the server responded with a status of 400 (Bad Request)
据报道,最后一种情况发生在http://DOMAIN-NAME/socket.io/?EIO=3&transport=polling&t=NLjf5hB&sid=h2aFFkOvNZtFc1DcAAAI
中。
然后,对于这些请求,我看到响应主体是:
{
"code": 1,
"message": "Session ID unknown"
}
这显然与前面的unknown sid
消息一致。我认为这意味着连接正在关闭,因为服务器认为会话ID不正确。
在我所做的研究中,我了解到在码头群中流量是以一种循环的方式分配的--也就是说,码头群充当了一个循环的负载均衡器。在这种情况下,使用Socket.IO的成功途径是实现粘性会话。
我在某个地方读到,NGINX中的粘性会话支持不适用于这种情况,Traefik可以支持这种情况。
在NGINX中,我使用了以下代理配置:
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-NginX-Proxy false;
proxy_pass http://todos;
proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
upstream todos {
ip_hash;
server todo:80 fail_timeout=1s max_fails=3;
keepalive 16;
}
这并没有改变这种行为--仍然是unknown sid
等等。因此,我转而使用Traefik,并且在Traefik的这一边查找文档时遇到了困难。这是我第一次使用Traefik。我能够使用Lets加密来实现HTTPS,而不是使用粘性会话。
为了配置Traefik,我使用命令行参数和Docker容器标签,这样整个配置都在Docker文件中。
traefik:
image: traefik:v2.0
restart: always
ports:
- "80:80" # <== http
- "8080:8080" # <== :8080 is where the dashboard runs on
- "443:443" # <== https
deploy:
replicas: 1
labels:
#### Labels define the behavior and rules of the traefik proxy for this container ####
- "traefik.enable=true" # <== Enable traefik on itself to view dashboard and assign subdomain to view it
- "traefik.http.routers.api.rule=Host(`monitor.DOMAIN-NAME`)" # <== Setting the domain for the dashboard
- "traefik.http.routers.api.service=api@internal" # <== Enabling the api to be a service to access
- "traefik.http.routers.api.entrypoints=web"
placement:
constraints:
- "node.hostname==srv1"
command:
- "--providers.docker.swarmmode=true"
- "--providers.docker.endpoint=unix:///var/run/docker.sock"
- "--providers.docker.watch=true"
- "--log.level=DEBUG"
- "--accesslog=true"
- "--tracing=true"
- "--api.insecure=true" # <== Enabling insecure api, NOT RECOMMENDED FOR PRODUCTION
- "--api.dashboard=true" # <== Enabling the dashboard to view services, middlewares, routers, etc...
- "--providers.docker=true" # <== Enabling docker as the provider for traefik
- "--providers.docker.exposedbydefault=false" # <== Don't expose every container to traefik, only expose enabled onesconfiguration file
- "--providers.docker.network=todo_webnet" # <== Operate on the docker network named web
- "--entrypoints.web.address=:80" # <== Defining an entrypoint for port :80 named web
- "--entrypoints.web-secured.address=:443" # <== Defining an entrypoint for https on port :443 named web-secured
- "--certificatesresolvers.mytlschallenge.acme.tlschallenge=false" # <== Enable TLS-ALPN-01 to generate and renew ACME certs
- "--certificatesresolvers.mytlschallenge.acme.email=E-MAIL-ADDRESS@DOMAIN-NAME" # <== Setting email for certs
- "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json" # <== Defining acme file to store cert
- "--certificatesresolvers.mytlschallenge.acme.httpChallenge.entryPoint=web"
volumes:
- /home/ubuntu/letsencrypt:/letsencrypt # <== Volume for certs (TLS)
- /var/run/docker.sock:/var/run/docker.sock # <== Volume for docker admin
networks:
- webnet
todo:
image: robogeek/todo-app:first-dockerize-redis
# ports:
# - "80:80"
networks:
- dbnet
- webnet
- redisnet
deploy:
replicas: 2
labels:
#### Labels define the behavior and rules of the traefik proxy for this container ####
- "traefik.enable=true" # <== Enable traefik to proxy this container
- "traefik.http.routers.todo.rule=Host(`DOMAIN-NAME`)" # <== Your Domain Name goes here for the http rule
- "traefik.http.routers.todo.entrypoints=web" # <== Defining the entrypoint for http, **ref: line 30
- "traefik.http.routers.todo.service=todo"
- "traefik.http.services.todo.loadbalancer.healthcheck.port=80"
- "traefik.http.services.todo.loadbalancer.sticky=true"
- "traefik.http.services.todo.loadbalancer.server.port=80"
- "traefik.http.routers.todo-secured.rule=Host(`DOMAIN-NAME`)" # <== Your Domain Name goes here for the http rule
- "traefik.http.routers.todo-secured.entrypoints=web-secured" # <== Defining the entrypoint for http, **ref: line 30
- "traefik.http.routers.todo-secured.service=todo"
- "traefik.http.routers.todo-secured.tls=true"
- "traefik.http.routers.todo-secured.tls.certresolver=mytlschallenge" # <== Defining certsresolvers for https
# - "traefik.http.routers.todo-app.middlewares=redirect@file" # <== This is a middleware to redirect to https
# - "traefik.http.routers.nginx-secured.rule=Host(`example.com`)" # <== Your Domain Name for the https rule
# - "traefik.http.routers.nginx-secured.entrypoints=web-secured" # <== Defining entrypoint for https, **ref: line 31
depends_on:
- db
- redis
dns:
- 8.8.8.8
- 9.9.9.9
environment:
- SEQUELIZE_CONNECT=models/sequelize-mysql-docker.yaml
- SEQUELIZE_DBHOST=db
- SEQUELIZE_DBNAME=tododb
- SEQUELIZE_DBUSER=dbuser
- SEQUELIZE_DBPASSWD=PASS-WORD-HIDDEN
- REDIS_ENDPOINT=redis
- NODE_DEBUG=redis
- REDIS_PASSWD=PASS-WORD-HIDDEN
- DEBUG=todos:*,ioredis:*,socket.io:*,engine
command: [ "./wait-for-it.sh", "-t", "0", "db:3306", "--", "node", "./app.mjs" ]
发布于 2020-10-28 18:00:59
查看Traefik论坛,我发现了以下内容:https://community.traefik.io/t/sticky-sessions-dont-work/1949
根据讨论,我将以下label
添加到todo
容器中:
- "traefik.http.services.todo.loadbalancer.sticky.cookie.name=StickySessionCookie"
现在它工作的很好,从1到4个容器到目前为止,它工作的很好。
发布于 2021-02-05 15:55:44
以防有人在HTTPS模式下运行。这是我的配置:
在labels
部分中的docker-复合文件中:
- "traefik.http.services.<service-name>.loadbalancer.sticky=true"
- "traefik.http.services.<service-name>.loadbalancer.sticky.cookie.name=StickyCookie"
- "traefik.http.services.<service-name>.loadbalancer.sticky.cookie.secure=true"
StickyCookie
更改为任意值。https://stackoverflow.com/questions/64567065
复制相似问题