ActionCable.server.pubsub
irb(main):004:0> pp AnyCable.config
#<AnyCable::Config
config_name="anycable"
env_prefix="ANYCABLE"
values:
rpc_host => "127.0.0.1:50051" (type=defaults),
rpc_pool_size => 30 (type=defaults),
rpc_max_waiting_requests => 20 (type=defaults),
rpc_poll_period => 1 (type=defaults),
rpc_pool_keep_alive => 1 (type=defaults),
rpc_server_args =>,
broadcast_adapter => "redis" (type=yml path=config/anycable.yml),
redis_url => "redis://192.168.72.98:20318/0" (type=defaults),
redis_sentinels => nil (type=defaults),
redis_channel => "__anycable__" (type=yml path=config/anycable.yml),
http_broadcast_url => "http://localhost:8090/_broadcast" (type=defaults),
http_broadcast_secret => nil (type=defaults),
log_file => nil (type=defaults),
log_level => :info (type=defaults),
log_grpc => false (type=yml path=config/anycable.yml),
debug => false (type=defaults),
http_health_port => nil (type=defaults),
http_health_path => "/health" (type=defaults),
version_check_enabled => true (type=defaults),
access_logs_disabled => true (type=yml path=config/anycable.yml),
persistent_session_enabled => false (type=defaults)>
Broadcasting lag could increase either when you have a lot of messages to broadcast or when you have a lot of clients. Currently, only a single broadcasting could happen at a time; usually, it’s pretty fast and only becomes noticeable when the throughput or the number of subscribed clients is high.
Add gem "anycable-rack-server" to you Gemfile and make sure your Action Cable adapter is set to :any_cable. That's it! We automatically start AnyCable Rack server for your at /cable path. but I am getting this error: WebSocket connection to 'ws://localhost:3334/cable' failed: Error during WebSocket handshake: Unexpected response code: 400 here is my config/environments/test.rb changes: # Enforce AnyCable patches to make it possible to use any_cable adapter for system tests
require "anycable/rails/actioncable/connection"
# TEMP: Remove me after final anycable 1.0.0 release
require "anycable/rack/version"
# Specify AnyCable WebSocket server URL to use by JS client
config.action_cable.url = "ws://localhost:3334/cable"
# Disable built-in Action Cable
config.action_cable.mount_path = nil
config.action_cable.disable_request_forgery_protection = true
# Run AnyCable Rack server at a custom path
config.any_cable_rack.mount_path = "/cable"Oh, I see, Thanks! However when I removed the config.action_cable.url line I got this in my rails app
ActionView::Template::Error: No Action Cable URL configured -- please configure this at config.action_cable.url
app/views/layouts/application.html.erb:4
app/controllers/users/sessions_controller.rb:11:in `new'so I changed it to config.action_cable.url = "/cable" but got the same error.
also, is websocket connection to ws://localhost:3334/cable correct? or should that be changed to something else?
so I just do WebSocket connect to "/cable" but got
/Users/jshen/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/grpc-1.31.1-universal-darwin/src/ruby/lib/grpc/generic/active_call.rb:29:in `check_status': 14:
failed to connect to all addresses. debug_error_string:{"created":"@1602860454.629484000","description":"
Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":4090,"referenced_errors":
[{"created":"@1602860453.508942000","description":"failed to connect to all
addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":394,"grpc_status":14}]}
(GRPC::Unavailable)when I added per README config.any_cable_rack.run_rpc = true I got
/Users/jshen/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/grpc-1.31.1-universal-darwin/src/ruby/lib/grpc/generic/client_stub.rb:47:
in `initialize': grpc cannot be used before and after forking (RuntimeError)RPC Connect: <AnyCable::ConnectionRequest: env: <AnyCable::Env: url: "http://127.0.0.1:59684/cable/", headers: {"cookie"=>"CSRF-TOKEN=xxxxxx"}, cstate: {}, istate: {}>>
Started "/cable/" [AnyCable] for at 2020-10-16 10:06:29 -0700
An unauthorized connection attempt was rejected
Finished "/cable/" [AnyCable] for at 2020-10-16 10:06:29 -0700 (Rejected)
RPC Disconnect: <AnyCable::DisconnectRequest: identifiers: "{}", subscriptions: [], env: <AnyCable::Env: url: "http://127.0.0.1:59684/cable", headers: {"cookie"=>"CSRF-TOKEN=xxxxx"}, cstate: {}, istate: {}>>
Finished "/cable" [AnyCable] for at 2020-10-16 10:06:29 -0700 (Closed)
Received pub/sub message: {"stream":"stage_questions:Z2lkOi8vYWRhaXIvU3RhZ2UvOTUw","data":"{\"stageQuestion\":{\"id\":1311,\"body\":\"Hopper\",\"votesEventRegistrationIds\":null,\"status\":\"asked\",\"votesCount\":1,\"eventRegistrationId\":2981,\"askerName\":null,\"askerInitials\":null,\"askerProfilePhotoUrl\":null},\"updateType\":\"NEW\"}"}anycable is rejecting connection somehow
Yes that got me further. However, now I wonder why this environmental variable causes anycable to hang indefinitely without any output.
13:43 $ RAILS_ENV=test bundle exec anycable --debug
(hangs forever)without it anycable runs fine
13:48 $ bundle exec anycable
Starting AnyCable gRPC server (pid: 69997, workers_num: 30)
AnyCable version: 1.0.1 (proto_version: v1)
gRPC version: 1.31.1
Serving Rails application from ./config/environment.rb
Broadcasting Redis channel: __anycable__
RPC server is starting...
RPC server is listening on 0.0.0.0:50051the reason I am trying with RAILS_ENV=test is because anycable seems to be not querying our test database with this error:
PG::UndefinedTable: ERROR: relation "users" does not exist
LINE 8: WHERE a.attrelid = '"users"'::regclass
Добрый день Владмир. Помогите пожалуйста. Обновил релиз anycable-rails (1.0.4). запускаю службу все ОК: Started command: bin/anycable-go --host=192.168.100.20 --debug --port=3334 --headers=cookies -ssl_cert=.ssh/server.crt -ssl_key=.ssh/server.key (pid: 219576)
DEBUG 2020-10-25T05:04:51.083Z context=main 🔧 🔧 🔧 Debug mode is on 🔧 🔧 🔧
INFO 2020-10-25T05:04:51.083Z context=main Starting AnyCable 1.0.2-ce5b4c5 (pid: 219576, open file limit: 1024)
DEBUG 2020-10-25T05:04:51.083Z context=disconnector Calls rate: 10ms
INFO 2020-10-25T05:04:51.083Z context=main Handle WebSocket connections at https://192.168.100.20:3334/cable
INFO 2020-10-25T05:04:51.083Z context=main Handle health connections at https://192.168.100.20:3334/health
INFO 2020-10-25T05:04:51.083Z context=rpc RPC controller initialized: localhost:50051 (concurrency: 28, proto_versions: v0,v1)
DEBUG 2020-10-25T05:04:51.083Z context=http Starting WebSocket server at https://192.168.100.20:3334
INFO 2020-10-25T05:04:51.083Z context=pubsub Subscribed to Redis channel: anycable
При установке соединения с фронтового приложения :
RPC Connect: <AnyCable::ConnectionRequest: env: <AnyCable::Env: url: "https://192.168.100.20:3334/cable", headers: {"cookies"=>"", "REMOTE_ADDR"=>"192.168.100.20"}, cstate: {}, istate: {}>>
Started "/cable" [AnyCable] for 192.168.100.20 at 2020-10-25 07:04:58 +0200
Token is not found
DEBUG 2020-10-25T05:04:58.089Z context=rpc Authenticate response: error_msg:"Token is not found"
ERROR 2020-10-25T05:04:58.089Z context=ws Websocket session initialization failed: Application error: Token is not found
Соединение через 'wss://192.168.100.20:3334/cable' пакет actioncable-vue
Сертификат самоподписной
В чем может быть проблема? Раньше работало. Какой ключ ему нужен?
Hi @palkan. We're shifting all our websockets to AnyCable at Exercism (https://exercism.io) as part of our version 3. I'm trying to be sure I understand the right way to deploy things, and hoping you could confirm I'm on the right tracks or correct me if I'm not!
We are deploying to AWS. My current setup is to have a machine (running on Fargate, but that's probably irrelevant) with docker containers for anycable-go, the anycable gRPC server, and the rails app. I then have a separate Redis server. That machine is sitting behind a load balancer. So far it works great. The websockets set up fine and everything's talking to each other nicely.
Where I'm unsure is if I add more of these machines behind the load balancer. Does having that separate Redis server give me the ability to have these machines sharing connection-knowledge. ie, if one machine broadcasts, but a different machine had been the one to establish the websocket, would the websocket still get broadcast. Or do these machines need to be able to communicate via gRPC directly? I'm feeling a little lost about how this bit works, so would appreciate your input.
If you'd like to jump on a call or do this via email or GH issue instead, please let me know! Thanks for all your work on Anycable :)
Hey Jeremy!
Does having that separate Redis server give me the ability to have these machines sharing connection-knowledge
Nope. RPC/WS servers do not communicate to each other, they rely on Redis to receive broadcasting events. Using separate Redis instances is only possible if you implement some kind of sharding: one Redis per application cluster (anycable-go and Rails apps).
In case of AnyCable, Redis is not heavily utilized, its load doesn't depend on the number of connections, thus, a single instance is usually enough. And you can use Redis clusters with sentinels for the sake of availability.
