Export - CSV (All fields)
Export - CSV (Current fields)
CONJ-547
Aurora failover based on read replica priorityCONJ-1207
New HaMode: sequential write, loadbalance read
Customer would like failover support found in connector-j, in other languages
Socket connections need to try all possible IP addresses for host
Aurora reader instances silently blacklisted when argument createDatabaseIfNotExist usedCONJ-686
Allow mixing TCP and socket hosts in failover configuration
new useSSL parameter option only for remote hosts
Failed to connect to Aurora cluster when "createDatabaseIfNotExist=true" option has specified
Support AWS RDS IAM Authentication with long living connection failover
Error in example of documentation in Failover / high availability parameters section
possible NPE on aurora when failover occur during connection initialisation
PrepareStatement failover handling : use master connection to a minimum
Unable to connect to galera non primary node for maintenance
Improve prepared statement on failover
failover : handle mono node completely
new high availability option : assureReadOnly
Best Practices for Aurora Cluster Reader Endpoint Failover
Text encoding concorrect on blob column
Permit aurora failover for a single-node cluster
Aurora Connection.isValid specific implementation
Wrong host address in exception message on failover
Aurora cluster endpoint detection fails when time_zone doesn't match system_time_zone
Thread stuck while executing an Alter table query while there was short network outage at mariaDB server and recovery
loadbalance distribution ensuring repartition after failover
can't make a connection when the Read Replica DB is in a hang state when SocketTimeout=0 set
failover re-execution using "redo transaction"
when a failover occurs, the connection reattemps is not limited by retriesAllDown option
load-balancing failover doesn't timeout
when a failover occurs, log replayed transaction
Failover during connection RESET command just throw exception
Deadlock in AwsIamCredentialPlugin
An SQL statement suddenly fails to execute
NullPointerException after failover happening on aurora cluster
Communication link failure with Aurora DB
Connections sometimes don't respect setCatalog
Option "allowMasterDownConnection" improvement on connection validation and Exceptions on master down
Insert Query failed after failover and not able to get master connection
Failover re-established connections present incorrect results
Failover must handle 70100 error code
autoReconnect=true on Basic Failover doesn't reconnect
Error reading SessionVariables is thrown when falling back to 'requestSessionDataWithShow'
failover might throw an unexpected exception with using "failover"/"sequential" configuration on socket error
Intermittent NullPointerException in prepareStatement
when only one slave and one master, connector/j only connect to master in some case
possible hang indefinitely using master/slave configuration and failover occur
retriesAllDown not working as expected
Permit connection creation to allow execution of read-only statements on slaves when master is down
MariaDB Driver Uses Read Replicas for non-Read-Only Connections
Aurora cluster automatic discovery
implementation of loadbalancing without failover