[
https://jira.jboss.org/browse/TEIID-1204?page=com.atlassian.jira.plugin.s...
]
Steve Hawkins resolved TEIID-1204.
----------------------------------
Resolution: Done
Re-enabled failover support with in a way that will work regardless of whether global
sesisons are used.
Will update the docs to indicate that failover is applicable to:
1. connection time
2. post-connection if it's an admin (such as adminshell) or autoFailover is true.
Post-connection failover works by sending a ping at most every second to test the
connection prior to use. If it fails a new instance will be selected prior to the
operation being attempted. The previous approach would retry, which is not appropriate
for non-idempotent operations. As before this is not true "transparent application
failover" we will not restart the transaction/query/recreate session scoped temp
tables, etc.
In both of the scenarios servers are connected to using a random selection policy. As
part of the load balancing issue, I look at introducing a programatic way to configure
selection.
Re-enable failover support
--------------------------
Key: TEIID-1204
URL:
https://jira.jboss.org/browse/TEIID-1204
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver
Affects Versions: 7.1
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1.1
Attachments: failover.patch
Failover support currently doesn't work due to sessions not being stored globally.
It has been determined that we will not store sessions globally - since that presents a
security risk and doesn't provide many benefits. So the failover support should feel
free to re-authenticate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira