![]() While I’m sure this works for replication and certain disaster recovery scenarios, I’m looking at multi master configurations, or with multiple datacenter configurations that are all “hot”, possibly removing the need for a centralized repository. In addition to simple failover configurations, it can also be configured for cascading configurations that allow for more interesting archival type configurations. I’m not sure if this is something that will change moving forward but today, a volume replicated is configured in a traditional Master/Slave configuration. Leveraging the native GlusterFS georeplication for a single volume is a one way street today. ( more info here) GlusterFS has native Geo Replication. It supports native clients, NFS, CIFS, HTTP, FTP, WebDAV and other protocols. GlusterFS is an open source project leveraging commodity hardware and the network to create scale-out, fault tolerant, distributed and replicated NAS solutions that are flexible and highly available. KISS oriented configuration What is GlusterFS? Right off the bat there were a few things that got my gears turning:Ī known and proven P2P protocol (monthly BitTorrent users are estimated at something insane like a quarter of a billion users) This ends up being effective for moving a lot of data across multiple devices and while I think it was initially designed for secure private dropbox style replication, I’ve been testing this as an alternative method of geo-replication between glusterfs clusters on Fedora. Synchronization is done securely via an encrypted (AES) bittorrent session. The concept is simple, using a local client on your desktop or laptop Sync will synchronize the contents of the selected folder to other remote Sync clients sharing the same key. While it took me a few minutes to wrap my head around what was going on and how this is being used, I’d have to say I’m impressed. Scraping multiple torrent info is possible with a static Client.Excerpted from Theron’s original blog, found here.Ī friend pointed me at a new bittorrent lab project, Sync. Requests for other paths will not be handled. ![]() The http server will handle requests for the following paths: /announce, /scrape. incomplete // get the peers who are in a particular torrent swarm server. complete // get the number of leechers for a particular torrent server. torrents ) // get the number of seeders for a particular torrent server. Var Client = require ( 'bittorrent-tracker' ) var requiredOpts = ) // get info hashes for all torrents in the tracker server Object. Tracker statistics available via web interface at /stats or JSON data at /stats.json.Used by popular clients: WebTorrent, peerflix, and playback.Comprehensive test suite (runs entirely offline, so it's reliable).Includes client & server implementations.The response includes a peer list that helps the client The requests include metrics from clients that help the tracker keep overall Node.js implementation of a BitTorrent tracker, client and server.Ī BitTorrent tracker is a web service which responds to requests from BitTorrentĬlients. Bittorrent-tracker Simple, robust, BitTorrent tracker (client & server) implementation
0 Comments
Leave a Reply. |