Comments (4)
Thanks and unfortunately, at the current point there is no way to restrict the znodes.
from burry.sh.
Hi @mhausenblas, thanks for your quick reply.
@maik-catrinque works with me, but he was not detailed and specific as necessary.
We got that there is no way to select a specific ZNode for backup, but is it considered "normal" for a backup using Burry to take 3-4 hours for a ZooKeeper cluster with 5 nodes and a data size of 10GB?
Just to add more context/information, the size of this zipped backup is around 3GB.
Another example: A new ZooKeeper cluster with 3 nodes and almost no data inside takes up to 2-3 minutes to backup. So if almost no data inside it can take 2-3 minutes, it might be a problem if this stores a lot of data.
Please, is there anything we could do to speed up the backup time or understand why it's taking so long?
Thanks in advance.
from burry.sh.
I see @gmenegatti and as much as I'd like to be of assistance here, unfortunately I don't have the cycles necessary to dedicate to this project. IOW: I'm not actively working on it anymore, but if anyone of your team wants to step up and contribute to address the performance issues you raised, you're more than welcome.
from burry.sh.
Got it @mhausenblas. Thanks for your support anyway.
Our team is not an expert in Golang. But we will give it a try.
from burry.sh.
Related Issues (20)
- Support Consul K/V store as infra service HOT 5
- Implement restore capabilities HOT 1
- Support Google Storage as target HOT 1
- Support Azure Storage as target
- Support Docker Engine as infra service
- SSL/TLS support? HOT 1
- Znode data for kafka topic znode not being copied. HOT 11
- custom snapshot id does not work HOT 1
- aux.go file is invalid for windows HOT 1
- Unable to restore Zookeeper in Kubernetes while running Kafka HOT 5
- Support ceph S3 Storage as target
- Target parameter is misleading HOT 5
- Add v3 data support HOT 2
- Upload backup snapshot as latest/last also
- ZK authentication HOT 4
- testing of etcd HOT 1
- S3 Instance Profile HOT 1
- Temporary nodes in zk become persistent nodes after recovery HOT 1
- When restoring zk data, node data cannot be overwritten
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from burry.sh.