ipfs-cluster/silent.go

// +build !debug,silent

package ipfscluster

func init() {
	l := "CRITICAL"
	for _, f := range facilities {
		SetFacilityLogLevel(f, l)
	}

	SetFacilityLogLevel("p2p-gorpc", l)
	SetFacilityLogLevel("swarm2", l)
	SetFacilityLogLevel("libp2p-raft", l)
}
Figured out globalSync and globalSync cid. Tests. More tests. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai> 2016-12-20 18:51:13 +00:00			`// +build !debug,silent`

			`package ipfscluster`

			`func init() {`
Fix #24: Auto-join and auto-leave operations for Cluster This is the third implementation attempt. This time, rather than broadcasting PeerAdd/Join requests to the whole cluster, we use the consensus log to broadcast new peers joining. This makes it easier to recover from errors and to know who exactly is member of a cluster and who is not. The consensus is, after all, meant to agree on things, and the list of cluster peers is something everyone has to agree on. Raft itself uses a special log operation to maintain the peer set. The tests are almost unchanged from the previous attempts so it should be the same, except it doesn't seem possible to bootstrap a bunch of nodes at the same time using different bootstrap nodes. It works when using the same. I'm not sure this worked before either, but the code is simpler than recursively contacting peers, and scales better for larger clusters. Nodes have to be careful about joining clusters while keeping the state from a different cluster (disjoint logs). This may cause problems with Raft. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai> 2017-02-02 22:52:06 +00:00			`l := "CRITICAL"`
Issue #18: Move Consensus and PeerMonitor to its own submodules License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai> 2017-03-10 16:24:25 +00:00			`for _, f := range facilities {`
			`SetFacilityLogLevel(f, l)`
			`}`

Fix #24: Auto-join and auto-leave operations for Cluster This is the third implementation attempt. This time, rather than broadcasting PeerAdd/Join requests to the whole cluster, we use the consensus log to broadcast new peers joining. This makes it easier to recover from errors and to know who exactly is member of a cluster and who is not. The consensus is, after all, meant to agree on things, and the list of cluster peers is something everyone has to agree on. Raft itself uses a special log operation to maintain the peer set. The tests are almost unchanged from the previous attempts so it should be the same, except it doesn't seem possible to bootstrap a bunch of nodes at the same time using different bootstrap nodes. It works when using the same. I'm not sure this worked before either, but the code is simpler than recursively contacting peers, and scales better for larger clusters. Nodes have to be careful about joining clusters while keeping the state from a different cluster (disjoint logs). This may cause problems with Raft. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai> 2017-02-02 22:52:06 +00:00			`SetFacilityLogLevel("p2p-gorpc", l)`
			`SetFacilityLogLevel("swarm2", l)`
			`SetFacilityLogLevel("libp2p-raft", l)`
Figured out globalSync and globalSync cid. Tests. More tests. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai> 2016-12-20 18:51:13 +00:00			`}`