seancribbs/ripple — comment on commit e5f24a5d54cd1f8f3bac3354cbbbd0c71b8a8d6d
File:  line 0
By aphyr:

I aimed for what was obviously safe. The goal of this recovery layer is to handle connection-level errors which:

a.) should result in the teardown+removal of this backend and
b.) can be safely retried on a newly constructed backend given that
c.) the node selection algorithm has a good probability of selecting a better node next time

I believe failed requests, mapreduce errors, etc, should be handled at a higher level. Besides, they'd cause the wrong behavior here.

If you look at the excon backend, it actually inserts its connection errors into this list. Constant isn't resolvable unless it's loaded. :/