mirror of
https://github.com/octoleo/syncthing.git
synced 2024-11-14 01:04:14 +00:00
916ec63af6
This is a new revision of the discovery server. Relevant changes and non-changes: - Protocol towards clients is unchanged. - Recommended large scale design is still to be deployed nehind nginx (I tested, and it's still a lot faster at terminating TLS). - Database backend is leveldb again, only. It scales enough, is easy to setup, and we don't need any backend to take care of. - Server supports replication. This is a simple TCP channel - protect it with a firewall when deploying over the internet. (We deploy this within the same datacenter, and with firewall.) Any incoming client announces are sent over the replication channel(s) to other peer discosrvs. Incoming replication changes are applied to the database as if they came from clients, but without the TLS/certificate overhead. - Metrics are exposed using the prometheus library, when enabled. - The database values and replication protocol is protobuf, because JSON was quite CPU intensive when I tried that and benchmarked it. - The "Retry-After" value for failed lookups gets slowly increased from a default of 120 seconds, by 5 seconds for each failed lookup, independently by each discosrv. This lowers the query load over time for clients that are never seen. The Retry-After maxes out at 3600 after a couple of weeks of this increase. The number of failed lookups is stored in the database, now and then (avoiding making each lookup a database put). All in all this means clients can be pointed towards a cluster using just multiple A / AAAA records to gain both load sharing and redundancy (if one is down, clients will talk to the remaining ones). GitHub-Pull-Request: https://github.com/syncthing/syncthing/pull/4648
35 lines
1.1 KiB
Go
35 lines
1.1 KiB
Go
package logrus
|
|
|
|
// A hook to be fired when logging on the logging levels returned from
|
|
// `Levels()` on your implementation of the interface. Note that this is not
|
|
// fired in a goroutine or a channel with workers, you should handle such
|
|
// functionality yourself if your call is non-blocking and you don't wish for
|
|
// the logging calls for levels returned from `Levels()` to block.
|
|
type Hook interface {
|
|
Levels() []Level
|
|
Fire(*Entry) error
|
|
}
|
|
|
|
// Internal type for storing the hooks on a logger instance.
|
|
type LevelHooks map[Level][]Hook
|
|
|
|
// Add a hook to an instance of logger. This is called with
|
|
// `log.Hooks.Add(new(MyHook))` where `MyHook` implements the `Hook` interface.
|
|
func (hooks LevelHooks) Add(hook Hook) {
|
|
for _, level := range hook.Levels() {
|
|
hooks[level] = append(hooks[level], hook)
|
|
}
|
|
}
|
|
|
|
// Fire all the hooks for the passed level. Used by `entry.log` to fire
|
|
// appropriate hooks for a log entry.
|
|
func (hooks LevelHooks) Fire(level Level, entry *Entry) error {
|
|
for _, hook := range hooks[level] {
|
|
if err := hook.Fire(entry); err != nil {
|
|
return err
|
|
}
|
|
}
|
|
|
|
return nil
|
|
}
|