Error handling requirements are not documented about redigo HOT 5 CLOSED

If there is an error writing to the network connection, then any future read or write will return the error. The code and examples leverage this by skipping error checks on intermediate writes.

This logic may not extend to Send when I add sharded connections. A Send to a sharded connection will fail when the keys span shards. I will need to do more design on sharded connections before I document the error checking rules.

from redigo.

Is it safe to ignore the error return value of Send() if I don't plan to use sharding?

from redigo.

Yes, it is safe if sharding is not used.

from redigo.

This might help on your design for sharded connections:
https://github.com/fiorix/txredisapi/blob/master/txredisapi.py#L1647

We have a HashRing class (consistent hashing algorithm by @gleicon) where we add nodes (connections), and select one for each operation based on the key. Not all operations are supported on sharded connections.

from redigo.

@fiorix Thanks the pointer. I'll take a look at it when I implement sharding.

from redigo.