Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Mar 18 09:37

    jondubois on master

    Bump minimist and cleanup packa… (compare)

  • Mar 18 09:31
    jondubois commented #526
  • Mar 18 09:10

    dependabot[bot] on npm_and_yarn

    (compare)

  • Mar 18 09:10
    dependabot[bot] commented #526
  • Mar 18 09:10
    jondubois closed #526
  • Mar 18 09:10
    jondubois commented #526
  • Mar 17 23:29
    dependabot[bot] labeled #526
  • Mar 17 23:29
    dependabot[bot] opened #526
  • Mar 17 23:29

    dependabot[bot] on npm_and_yarn

    Bump minimist from 1.2.0 to 1.2… (compare)

  • Mar 17 03:40
    Energytechglobal closed #525
  • Mar 17 03:40
    Energytechglobal commented #525
  • Mar 15 05:54
    frank-dspeed commented #525
  • Mar 12 13:13
    Energytechglobal commented #525
  • Mar 11 17:44
    nelsonzheng edited as member
  • Mar 11 17:44
    lihan edited as member
  • Mar 10 09:33
    jondubois commented #525
  • Mar 10 09:26
    jondubois commented #525
  • Mar 09 14:16
    Energytechglobal opened #525
  • Feb 17 07:47
    jondubois commented #524
  • Feb 17 06:35
    rasoulivand opened #524
Q. Wade Billings
@qwade-ambi
Hello, I need some help with socketcluster brokers and state servers ... I am getting an obscene number of these errors in my state server and I am not sure how to solve for them.
{ TimeoutError: Event response for "sccBrokerJoinCluster" timed out at Timeout.setTimeout [as _onTimeout] (/usr/src/node_modules/socketcluster-server/serversocket.js:1238:19) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10) name: 'TimeoutError', message: 'Event response for "sccBrokerJoinCluster" timed out' }
Jonathan Gros-Dubois
@jondubois
@qwade-ambi What version of SC/SCC are you using? Do scc-state and scc-broker versions match? You're running them in Docker?
How many nodes in your cluster approximately?
What sort of CPU usage do you see on each instance?
Where did you obtain this log from? scc-state or scc-broker or from your socketcluster instance (scc-worker)?
I would check for version compatibility; in SCC, the major version number of all the components must match
So for example, scc-broker v8.x.x must be paired with scc-state v8.x.x
Jonathan Gros-Dubois
@jondubois
Secondly, I would check CPU usage of the scc-broker instances
Maybe you need to add more scc-broker instances to your cluster. Could be that they're so busy that they're timing out and you need to add capacity
I would also check scc-state CPU usage
Jonathan Gros-Dubois
@jondubois
Also it could be that your scc-broker instances cannot connect to your scc-state instance; maybe the scc-state port is blocked or there is a proxy in between which is killing the connection
It could be any of these things
Q. Wade Billings
@qwade-ambi
This is all great stuff and I will check on all of it .. thank you.
State Server: socketcluster/scc-state:v8.0.0
Broker: socketcluster/scc-broker:v8.0.0
Q. Wade Billings
@qwade-ambi
Broker environment:
Environment:
  SCC_STATE_SERVER_HOST:        scc-state-service
  SOCKETCLUSTER_WORKERS:        1
  SOCKETCLUSTER_BROKERS:        1
  SCC_INSTANCE_IP:               (v1:status.podIP)
  SCC_BROKER_SERVER_LOG_LEVEL:  2
Ratio: 1 state server to 4 brokers
All running on AWS EKS
The log snippet came from the state server
Checked connectivity from broker -> state via telnet scc-state-service 7777 and it connected just fine
on all instances
of the broker server that is ^^
Q. Wade Billings
@qwade-ambi
I am wondering about these environment settings in the broker now that I am looking at them
SOCKETCLUSTER_WORKERS: 1
SOCKETCLUSTER_BROKERS: 1
should those be set or left unset for any environment !dev?
Q. Wade Billings
@qwade-ambi
Also, are there broker -> state connection timeout settings that I can play with that might help these errors abate?
Kevin Boon
@inQonsole
Where did you get the error, on the scc-state or one of the brokers ?
it looks like the broker is unable to reach the scc-state server, since it's waiting for a response back but it times out, it might show that the connectivity works via telnet but it could be configuration issue with how the broker is trying to resolve the host
Paul T.
@wilensky

Hi there! I'm wondering how one can produce/trigger an event/rpc from another event/rpc :question:
The reason I want to do that is to allow several sources to trigger same event or proxy events from external sources to internal events.

E.g. some logout event can be reported by external system via Redis Pub/Sub or REST API, but I want that trigger existing event handler for this operation. It may seems not straightforward or maybe bad example but I have a case where I am subscribed to redis pub/sub for certain event and I want that event to trigger a native SC event.

Hasan Shahriar Masud
@hsmasud
Hi, I want to host socketcluster in aws eks. But I could not found any document how to do that. Can anyone share any document which can help.
Frank Lemanschik
@frank-dspeed
hmmmm the general documentation does cover that i think
Sena Ji
@sena-ji
Hello, I am a beginner coder and I want to build a phone app that allows people to chat offline through lan connection. Is there any documentation that I could read about sockets that might help?
Or is this done through some other method besides sockets?
Frank Lemanschik
@frank-dspeed
Sena Ji simply code it as it would be a online app
put into the phone app all 3 components and configure leader election for scc-state
but it is a bigger project i think there is nothing already coded like leader election or hot standby for scc around
Frank Lemanschik
@frank-dspeed
or wait even better would be to replace scc-state with some network lookup
that is also possible as you have control over the network you could get a fixed list of client-ip's
Q. Wade Billings
@qwade-ambi
Silly question time, would using the following versions together be recommended on k8s?
  • Socketcluster: 14.4.2
  • Socketclsuter-client: 16.0.1
  • Socketcluster-server: 16.0.0
  • SCC-broker: 8.0.0
  • SCC-State: 8.0.0
Kevin Boon
@inQonsole
@qwade-ambi the Socketcluster package should be : 16.0.1 not 14.4.2
Sena Ji
@sena-ji
@frank-dspeed are there any documents or examples I could read that shows how to replace scc-state with some network lookup?
Frank Lemanschik
@frank-dspeed
no you need to do that or pay some one
no one did it befor
Sena Ji
@sena-ji
Got it! Thank you
Q. Wade Billings
@qwade-ambi
@inQonsole that is what I was afraid of. thanks for confirming for me.
Kevin Boon
@inQonsole
@qwade-ambi No problem