Problem

When using scanIteration() with JedisSentineled, connections are leaked from the pool and never returned.

SentineledConnectionProvider uses the default ConnectionProvider.getConnectionMap() implementation, which allocates a raw Connection from the pool. JedisCommandIterationBase uses this connection directly (line 68-69) without returning it to the pool.

Solution

Override getConnectionMap() and getPrimaryNodesConnectionMap() in SentineledConnectionProvider to return the pool itself, consistent with PooledConnectionProvider:

@Override
public Map<?, Pool<Connection>> getConnectionMap() {
  return Collections.singletonMap(currentMaster, pool); 
}
 
@Override
public Map<?, Pool<Connection>> getPrimaryNodesConnectionMap() {
   return Collections.singletonMap(currentMaster, pool);
}

This allows JedisCommandIterationBase to properly manage connections using try-with-resources (lines 71-73).

Note on volatile pool: The iteration captures the pool reference at construction time. Connections from the old pool remain valid even if failover occurs during iteration.

Note on returning a Pool<Connection> by getConnectionMap vs Connection to:

• JedisCommandIterationBase already handles both Connection and Pool types (lines 68-76)
• getConnectionMap() is only used internally by iteration classes
• This change aligns SentineledConnectionProvider with PooledConnectionProvider's existing behavior
• Previous behavior would cause connections to be exhausted using multilpe times scan operaions

Fixes #4323