swarm icon indicating copy to clipboard operation
swarm copied to clipboard

Easy clustering, registration, and distribution of worker processes for Erlang/Elixir

Results 46 swarm issues
Sort by recently updated
recently updated
newest added

Noticed a lot of this message in our logs: ``` remote tracker on #{remote_node} went down during registration, retrying operation.. ``` It seems to happen randomly, but I think this...

Closes https://github.com/bitwalker/swarm/issues/127 I'm really not sure if this is correct or not, but the tests seem to pass and the "unrecognized cast" messages are now gone. I'm not sure whether...

Swarm: 3.2.1 Elixir: 1.6.1 Erlang: 20.2.2 Suppose we have two nodes A and B. We have a worker W which was spawned on node A. Now node A crashes and...

enhancement
question

We've shortly switched to swarm in the quantum library. We're seeing two errors when we do agressive up / down scaling. These errors may very well be errors on the...

bug
investigating
tracker

I have a service `calculator` and the `investigator` running through the `libcluster`. but when I register my service, sometimes something strange happens. for example: When I start the `calculator` service...

Hi, I'm testing the concurrency of swarm using my in-house tool (will be released soon!). I've found several deadlocks when bootstrapping swarm in distributed settings. Here is one potential sketch...

First off, thanks for the awesome library! Sure makes clustering easy when running kubernetes. I ran into an issue today where I want to be able to send a message...

I'm having an issue similar to #60, reproducible very often when I bring up containers with the app at roughly the same time. Looks like each node is waiting for...

investigating

To recap, the tracker uses an implementation of an Interval Tree Clock for resolving the causal history of replicated events. My understanding of ITC is that a scenario plays out...

We're running a small application in our kubernetes cluster and we're encountering a few problems. Specifically, we've got nodes that will deadlock on startup like #91 and clocks getting out...

bug
investigating