Redis jedispoolconfig parameter Configuration

Configuration of the Jedis pool,

maxactive : controls how many Jedis instances a pool can allocate, obtained through Pool.getresource ();

If the assignment is 1, there is no limit, and if the pool is already assigned a maxactive Jedis instance, then the state of the pool is exhausted.
maxidle: controls the maximum number of Jedis instances in a pool that have a status of idle;

whenexhaustedaction :
maxwait :

Testonborrow: Whether alidate operations are performed in advance when a Jedis instance is borrow, and if true, the resulting Jedis instances are available;
Testonreturn: Whether the validate operation is performed in advance when the return is given to the pool;
Testwhileidle: If true, indicates that there is an idle object Evitor thread that scans the idle object, and if the validate fails, the object is dropped from the pool ; This item is only meaningful if the Timebetweenevictionrunsmillis is greater than 0;

Timebetweenevictionrunsmillis: Indicates the number of milliseconds to sleep between idle object Evitor two scans;
Numtestsperevictionrun: Indicates the maximum number of objects per scan of the idle object evitor;
Minevictableidletimemillis: Represents the minimum time at which an object stays in the idle state before it can be scanned and evicted by an idle object evitor ; This item is only meaningful if the Timebetweenevictionrunsmillis is greater than 0;

Softminevictableidletimemillis: On the basis of minevictableidletimemillis, at least minidle objects have been added to the pool. If the -1,evicted does not expel any objects according to the idle time. If minevictableidletimemillis>0, this setting is meaningless and only makes sense if the Timebetweenevictionrunsmillis is greater than 0;

LIFO:borrowobject when the object is returned, it is the Default_lifo (last on first out, the most frequently used queue similar to the cache) and, if False, the FIFO queue;

Redis jedispoolconfig parameter Configuration