Lines Matching refs:is
4 The connection pool is an object inside the client that is responsible for
9 is to manage this set of unruly connections and try to provide the best behavior
12 If a connection pool is unable to find an alive node to query against, it
13 returns a `NoNodesAvailableException`. This is distinct from an exception due to
20 When the next request is sent to the client, nodes 1-9 are still considered
21 "dead", so they are skipped. The request is sent to the only known alive node
22 (#10), if this node fails, a `NoNodesAvailableException` is returned. You
24 applies to retries against alive nodes. In this case, only one node is known to
25 be alive, so `NoNodesAvailableException` is returned.
34 alive when the client initializes. If a node fails a request, it is marked as
35 `dead` for 60 seconds and the next node is tried. After 60 seconds, the node is
51 Note that the implementation is specified via a namespace path to the class.
59 scripts but tends to be additional overhead that is unnecessary for average PHP
71 Note that the implementation is specified via a namespace path to the class.
79 alive. It is a simple pool of static hosts.
81 The `SimpleConnectionPool` is not recommended for routine use but it may be a
93 Note that the implementation is specified via a namespace path to the class.
99 Unlike the two previous static connection pools, this one is dynamic. The user
113 Note that the implementation is specified via a namespace path to the class.
163 implementation has a compatible constructor (since it is not defined in the
215 many languages, it is. In PHP, the conversation is a bit more nuanced.
217 Because PHP is a share-nothing architecture, there is no way to maintain a
218 connection pool across script instances. This means that every script is
220 script is re-run.
222 Sniffing is a relatively lightweight operation (one API call to
230 In reality, if your script only executes a few queries, the sniffing concept is
234 For this reason the default connection pool is currently the