dns-only loadbalancing on a single mercury node with mutiple backends
rdoorn opened this issue · 1 comments
rdoorn commented
when mercury acts as a dns only loadbalancer (without a proxy)
the dns entry returned should be that of the hosts that are up (with a loadbalance algorithm)
tricky part: shared dns entries if 2 mercury clusters share dns, and also loadbalance locally
reason beeing, if 2 mercury instances share dns entreis, and balance across, if 1 mercury node dies, so does the dns entry, which is a problem in active-standby situations, if the backend behind the dying mercury node is the available one, and mercury no longer sends its dns entry to the secondary mercury node.
A S
| |
m - m