Giters
weaveworks
/
mesh
A tool for building distributed applications.
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
867
Watchers:
79
Issues:
47
Forks:
107
weaveworks/mesh Issues
Is this project still supported by weaveworks maintainers?
Updated
a year ago
Comments count
1
Project status? Is this dead?
Closed
a year ago
Comments count
2
Allow clients to set the "advertised address"
Updated
3 years ago
Comments count
1
Whether the Router will ignore the localPeer in Router.Peers
Updated
3 years ago
Provide a simple usage example
Updated
3 years ago
Example for mesh to build a distributed app
Updated
3 years ago
runtime error: invalid memory address or nil pointer dereference
Closed
4 years ago
Comments count
1
Thousands to millions of peers?
Closed
4 years ago
encryptedTCPSender.Send() holds a lock over a TCP send
Updated
4 years ago
Comments count
1
TCP sends block forever
Updated
4 years ago
Restarted peers do not get initial gossip
Closed
4 years ago
Comments count
2
High memory/CPU utilization for moderately sized cluster
Closed
4 years ago
Comments count
5
high rate of peer.routes() calculation resuting from gossip broadcasts
Closed
4 years ago
Comments count
1
Topology update broadcasts are sent once per route calculation
Closed
4 years ago
Comments count
1
randomNeighbours selection is biased
Closed
4 years ago
rate-limit routes calculation done when a gossip topology update is received
Closed
5 years ago
high rate of Peers.garbageCollect() calls resulting from topology gossip
Closed
5 years ago
in fullly connected mesh topolgy, topology update gossip's can get chatty
Closed
5 years ago
cached broadcast routes are reset when performing routes.calculate()
Closed
5 years ago
Comments count
4
make gossipInterval configurable
Closed
5 years ago
Comments count
1
redundant broadcast topology update in case of fully-connected mesh of node
Updated
5 years ago
Comments count
1
optimise Peer.Routes() for fully connected mesh of node topology
Updated
5 years ago
There is something wrong
Closed
6 years ago
Make the maintenance process work
Updated
6 years ago
Observer for Change of peers
Updated
7 years ago
Add IPv6 support
Updated
7 years ago
Comments count
5
When passed a DNS name, InitiateConnection only resolves one record; all records would be better
Updated
7 years ago
Comments count
1
Remove assumptions about peer ports
Updated
7 years ago
Panic on creating duplicate Gossip?
Closed
7 years ago
Comments count
4
How to change peers?
Closed
7 years ago
Comments count
2
Run tests on alternative tags
Updated
7 years ago
SurrogateGossiper can accumulate infinite amounts of data
Updated
7 years ago
surrogateGossiper can form a feedback loop
Closed
7 years ago
panic due to remote address discrepancy
Closed
8 years ago
example client/server to transmit data
Updated
8 years ago
Comments count
2
Weave mesh comments
Closed
8 years ago
Comments count
2
How does Mesh compare with Serf from Hashicorp?
Closed
8 years ago
Comments count
3
Clarify documentation on copying
Updated
8 years ago
Change concrete *log.Logger to mesh.Logger interface
Updated
8 years ago
Comments count
2
Don't use global logger; take a logger as a parameter
Closed
8 years ago
Unexport LocalConnection, favor an e.g. Overlayer interface
Updated
8 years ago
New linter error
Closed
8 years ago
Increment-only counter example should be a proper delta CRDT
Updated
8 years ago
Define a special broadcast meshconn.MeshAddr
Updated
8 years ago
Race condition: Local peer connections may be modified without taking a lock
Updated
8 years ago
Peer restarts can be squelched
Updated
8 years ago
consistent application of channel input/output capability restrictions
Closed
8 years ago