-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Balancing integration * Signals handling SIGHUP triggers configuration reload, SIGINT gracefully shutsdown server
- Loading branch information
Showing
76 changed files
with
2,784 additions
and
2,177 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,8 +15,8 @@ | |
Akubra is a simple solution to keep an independent S3 storages in sync - almost | ||
This comment has been minimized.
Sorry, something went wrong. |
||
realtime, eventually consistent. | ||
|
||
Keeping synchronized storage clusters, which handles great volume of new objects | ||
(about 300k obj/h), is the most efficient by feeding them with all incoming data | ||
Keeping synchronized storage clusters, which handles great volume of new objects, | ||
This comment has been minimized.
Sorry, something went wrong.
wookie41
Contributor
|
||
is the most efficient by feeding them with all incoming data | ||
at once. That's what Akubra does, with a minimum memory and cpu footprint. | ||
|
||
Synchronizing S3 storages offline is almost impossible with a high volume traffic. | ||
|
@@ -37,6 +37,11 @@ It also backtracks to older cluster when requested for not existing object on | |
target cluster. This kind of events are logged, so it's possible to rebalance | ||
clusters in background. | ||
|
||
### Multi cloud cost optimization | ||
This comment has been minimized.
Sorry, something went wrong.
wookie41
Contributor
|
||
While all objects has to be written in every storage from shard, not all storages | ||
has to be read. With load balancing and storage prioritization akubra will peak | ||
cheapest one. | ||
|
||
## Build | ||
|
||
### Prerequisites | ||
|
@@ -153,32 +158,6 @@ Service: | |
IdleConnTimeout: 2s | ||
ResponseHeaderTimeout: 2s | ||
|
||
# MaxIdleConns see: https://golang.org/pkg/net/http/#Transport | ||
# Default 0 (no limit) | ||
MaxIdleConns: 0 | ||
# MaxIdleConnsPerHost see: https://golang.org/pkg/net/http/#Transport | ||
# Default 100 | ||
MaxIdleConnsPerHost: 100 | ||
# IdleConnTimeout see: https://golang.org/pkg/net/http/#Transport | ||
# Default 0 (no limit) | ||
IdleConnTimeout: 0s | ||
# ResponseHeaderTimeout see: https://golang.org/pkg/net/http/#Transport | ||
# Default 5s | ||
ResponseHeaderTimeout: 5s | ||
# DisableKeepAlives see: https://golang.org/pkg/net/http/#Transport | ||
# Default false | ||
|
||
DisableKeepAlives: false | ||
|
||
# Maximum accepted body size | ||
BodyMaxSize: "100M" | ||
# Maximum number of incoming requests to process at once | ||
MaxConcurrentRequests: 200 | ||
# Backend in maintenance mode. Akubra will skip this endpoint | ||
|
||
# MaintainedBackends: | ||
# - "http://s3.dc2.internal" | ||
|
||
# List request methods to be logged in synclog in case of backend failure | ||
SyncLogMethods: | ||
- PUT | ||
|
Oops, something went wrong.
-> Akubra is a simple solution to keep independent S3 storages in sync
an
is invalid with plural