I've noticed two problems with stratum backup pools, that still exist on 2.10.1. The bigger problem is that stratum backup pools can become permanently dead. This is only happening on my rigs with wireless connections, so maybe it's a problem with latency / packet loss? Second problem is that with failover-only disabled, most leaked shares seem to go to my getwork backup pool, even though it's last on the list. I have two stratum backup pools with higher priority than the getwork pool, but they rarely (if ever) get leaked shares. This is only a small matter, since share leakage is very low.
I need to investigate the dead pool issue. I haven't seen it happen myself.
As for leaking shares, stratum and gbt pools actually don't leak shares at all with or without failover-only mode. You only get leakage if the primary pool is getwork and you're not in failover only mode.
Here's how the shares end up to pool 3, the only getwork pool, when primary pool connection drops:
[2012-12-16 18:14:05] Accepted 0b30f6dd Diff 22/4 GPU 0 pool 0
[2012-12-16 18:14:32] Accepted 1717f2fd Diff 11/4 GPU 0 pool 0
[2012-12-16 18:16:02] Lost 2 shares due to stratum disconnect on pool 0
[2012-12-16 18:16:37] Accepted 481563e1 Diff 3/1 GPU 1 pool 3
[2012-12-16 18:16:52] Accepted 3752b425 Diff 4/1 GPU 0 pool 3
[2012-12-16 18:16:53] Accepted ed86b60d Diff 1/1 GPU 0 pool 3
[2012-12-16 18:17:02] Pool 0
http://mint.bitminter.com:3333 not responding!
[2012-12-16 18:17:02] Switching to
http://us1.eclipsemc.com:3333[2012-12-16 18:17:16] Accepted 33ec2056 Diff 4/1 GPU 1 pool 3
[2012-12-16 18:17:24] Accepted 3c342f03 Diff 4/1 GPU 0 pool 1
Some shares go to pool 3 before cgminer switches to my first backup pool. This also happens during startup, but it's only a share or two.
"Lost 2 shares due to stratum disconnect on pool 0" happens because stratum can't handle disconnects currently, right?
