Documentation
¶
Overview ¶
Package conn provides a safe MySQL connection pool with human-friendly error and metrics.
Index ¶
Constants ¶
This section is empty.
Variables ¶
var ( // ErrConnCannotConnect is returned when a connection cannot be made because // MySQL is down or unreachable for any reason. This is usually because // MySQL is down, but it could also indicate a network issue. If this error // occurs frequently, verify the network connection and MySQL address. If it // occurs infrequently, it could indicate a transient state that will // recover automatically; for example: a failover. Connector.Error returns true // with this error. ErrConnCannotConnect = errors.New("cannot connect") // ErrConnLost is returned when the connection is lost, closed, or killed // for any reason. This could mean MySQL crashed, or the KILL command was used // to kill the connection. Lost is distinct from down: a connection can only // be lost if it was previously connected. If MySQL is up and ok, this could // indicate a transient state that will recover automatically. If not, // ErrConnCannotConnect will probably be returned next when the driver tries // but fails to reestablish the connection. Connector.Error returns true with // this error. ErrConnLost = errors.New("connection lost") // ErrQueryKilled is returned when the KILL QUERY command is used. This only // kills the currently active query; the connection is still ok. This error // is not connection-related, so Connector.Error returns false. ErrQueryKilled = errors.New("query killed") // ErrReadOnly is returned when MySQL read-only is enabled. This error is not // connection-related, so Connector.Error returns false. ErrReadOnly = errors.New("server is read-only") // ErrDupeKey is returned when a unique index prevents a value from being // inserted or updated. This error is not connection-related, so Connector.Error // returns false. ErrDupeKey = errors.New("duplicate key value") // ErrTimeout is returned when a context timeout happens. This error is not // connection-related, so Connector.Error returns false. ErrTimeout = errors.New("timeout") )
Functions ¶
func Down ¶
Down returns true if the error indicates MySQL cannot be reached for any reason, probably because it's not running. Down is distinct from lost: it's a network-level error that means MySQL cannot be reached. MySQL could be up and ok, but particular connections are failing, so from the program's point of view MySQL is down.
func Lost ¶
Lost returns true if the error indicates the MySQL connection was lost for any reason. Lost is distinct from down: a connection can only be lost if it was previously connected. A connection can be lost for many reasons. MySQL could be up and ok, but particular connections were lost. For example, the KILL command causes a lost connection.
func MySQLErrorCode ¶
MySQLErrorCode returns the MySQL server error code for the error, or zero if the error is not a MySQL error.
Types ¶
type Connector ¶
type Connector interface { // Open opens a sql.Conn from the pool. It returns the error from sql.Conn, // if any. The caller should pass the error to Error to return a high-level // error exported by this package. Open(context.Context) (*sql.Conn, error) // Close closes a sql.Conn by calling its Close method. The caller should call // this method instead of calling conn.Close directly. Do not call both, but // one or the other must be called to return the connection to the pool. It // returns the error from conn.Close, if any. Close(*sql.Conn) error // Error returns true if the given error indicates the connection was lost, // else it returns false. If true, the caller should wait and retry the // operation. The driver will attempt to reconnect, but it usually takes // one or two attempts after the first error before the driver reestablishes // the connection. This is a driver implementation detail that cannot be // changed by the caller. // // The returned error can be different than the given error. Certain low-level // MySQL errors are returned as high-level errors exported by this package, // like ErrQueryKilled and ErrReadOnly. These high-level errors are common // and usually require special handling or retries by the caller. The caller // should check for and handle these high-level errors. Other errors are // probably not recoverable and should be logged and reported as an internal // error or bug. // // If the given error is not a MySQL error or nil, the method does nothing // and returns false and the given error. // // The caller should always call this method with any error from any code // that used a sql.Conn. See packages docs for the canonical workflow. Error(error) (bool, error) }
A Connector creates sql.Conn without exposing how connections are made. Code that connects to MySQL is passed a Connector and it opens and closes unique connections as needed. Every connection open must be closed, else connection will be leaked.
type Pool ¶
type Pool struct {
// contains filtered or unexported fields
}
Pool represents a MySQL connection pool. It implements the Connector interface and exposes Stats.
func (*Pool) Error ¶
Error determine if the given error is connection-related and possibly transforms it into a higher-level error exported by this package. See Connector.Error for more details.
func (*Pool) Stats ¶
Stats returns the stats since the last call to Stats. Stats are never reset. The Open stat is not always accurate. The driver updates it lazily, so it can be higher than the actual number of currently open connections.
The caller is expected to poll Stats at regular intervals. It is safe to safe to call concurrently.
type Stats ¶
type Stats struct { *sync.Mutex Ts int64 // Unix timestamp when stats were returned Open int // sql.DBStats.OpenConnections, not always accurate (gauge) OpenCalls int // All calls to Open (counter) Opened uint // Successful calls to Open (counter) Closed uint // All calls to close (counter) Timeout uint // Timeouts during calls to Open (counter) Lost uint // Lost connections (counter) Down uint // ErrConnCannotConnect errors (counter) }
Stats represents counters and gauges for connection-related events. A Pool saves and exposes stats.