The GAE standard environment can have transient connection reset events. When using redis-py, it is typically recommended that the user wrap the redis-py client with something that can handle and retry on connection resets. It appears that a redis-py instance can be passed to Cloud NDB but this feels like an experience that could be improved?

On the whole, connection resets are somewhat a fact of life in GAE standard net stack, and users of redis-py connection pools (NDB library looks like one of those "users") frequently grapple with this issue. The ask is whether we might make NDB more resilient (can NDB retry?) in the face of the inevitable resets.