Hi,
I'm looking at setting up a small cluster of P2Pool nodes for anybody to use, and was wondering what a good high-availability configuration looks like.
Since I'm going to set up more than one server, I'd ideally like the mining clients to automatically switch over to a different server in the cluster if the server they're connected to goes down. I can think of two ways to do this:
1. DNS. I'll provide a server address such as http://us.example.com/. "us.example.com" will resolve to multiple IP addresses (multiple A records), each of which is a node in the cluster. Do current miners support this form of failover?
2. Load balancing. If the miners do not support DNS-based failover, I could put a load balancer in front of the actual nodes in the cluster. However, I'm concerned that the load balancer itself will add some latency to the connections, so I'd rather not go this route.
Can somebody shed some light on this? Thanks!
- Nik.
(I'm not a newbie to Bitcoin. Just posting here because I just signed up for a new account and can only post in this forum. Would be great if somebody could move this thread to the appropriate Mining/Pools subforum.)
Topic: High-availability/redundant mining pool server setup (Read 383 times)
Jump to: