Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
-
None
Description
from stackoverflow
A Timeout of 5s with Aurora probably signify that amazon proxy discard socket remaining ip when having read packet.
If so, the proxy has a race condition when usePipelineAuth not seen in tests.
This have to be send to amazon team, and pipelining functionality disabled when using aurora.
Attachments
Issue Links
- relates to
-
CONJ-477 Aurora not compatible with option usePipelineAuth
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
from [stackoverflow|http://stackoverflow.com/questions/44002312/sqltransientconnectionexception-after-upgrading-mariadb-connector]
A Timeout of 5s with Aurora signify probably that amazon proxy discard socket when having read query. If so, the proxy has a race condition when usePipelineAuth not seen in tests. |
from [stackoverflow|http://stackoverflow.com/questions/44002312/sqltransientconnectionexception-after-upgrading-mariadb-connector]
A Timeout of 5s with Aurora probably signify that amazon proxy discard socket remaining ip when having read packet. If so, the proxy has a race condition when usePipelineAuth not seen in tests. This have to be send to amazon team, and pipelining functionality disabled when using aurora. |
Fix Version/s | 1.6.1 [ 22550 ] | |
Fix Version/s | 2.0.2 [ 22551 ] |
Component/s | aurora [ 14008 ] | |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 80834 ] | MariaDB v4 [ 134981 ] |
dupplicate
CONJ-477