Edward Archibald (JIRA)
2010-01-16 03:24:47 UTC
Provide a means to support application-transparent session-consistent reads
---------------------------------------------------------------------------
Key: MYO-115
URL: https://forge.continuent.org/jira/browse/MYO-115
Project: Tungsten Connector
Type: Bug
Reporter: Edward Archibald
Assigned to: Gilles Rayrat
Many customers cannot or are unwilling to modify applications to take advantage of session consistency. At present, the only way to do this is to have applications use transaction boundaries to tell us whether or not there is a write or read-only operation and they must also pass us a sessionID. The work in progress provides the following for customers who are willing to use the Connector - and these changes work in passthrough mode as well.
There are two basic configurations:
The first involves configuring the connector such that there is only ever a single session for all connections. Applications that can take advantage of such a configuration are primarily those who do writes infrequently and when they do writes, they are primarily done in batches. When this is the case, the configuration referred to here guarantees that the slaves are used most of the time and that only during the window of the writes concurrently with applications doing reads, would read requests be routed to the master.
The second involves configuring the connector so that every connection that is made through the connector automatically generates a sessionid that is associated with only that connection. Applications that can take advantage of such a configuration either create connections and use them for groups of read and write operations or create pools of connections. Again, the applications also need to have a fairly low write rate but provided that the write rate is low, and that connections can more-or-less be accessed by the same application 'user', the chances for having slave 'hits' are pretty high.
---------------------------------------------------------------------------
Key: MYO-115
URL: https://forge.continuent.org/jira/browse/MYO-115
Project: Tungsten Connector
Type: Bug
Reporter: Edward Archibald
Assigned to: Gilles Rayrat
Many customers cannot or are unwilling to modify applications to take advantage of session consistency. At present, the only way to do this is to have applications use transaction boundaries to tell us whether or not there is a write or read-only operation and they must also pass us a sessionID. The work in progress provides the following for customers who are willing to use the Connector - and these changes work in passthrough mode as well.
There are two basic configurations:
The first involves configuring the connector such that there is only ever a single session for all connections. Applications that can take advantage of such a configuration are primarily those who do writes infrequently and when they do writes, they are primarily done in batches. When this is the case, the configuration referred to here guarantees that the slaves are used most of the time and that only during the window of the writes concurrently with applications doing reads, would read requests be routed to the master.
The second involves configuring the connector so that every connection that is made through the connector automatically generates a sessionid that is associated with only that connection. Applications that can take advantage of such a configuration either create connections and use them for groups of read and write operations or create pools of connections. Again, the applications also need to have a fairly low write rate but provided that the write rate is low, and that connections can more-or-less be accessed by the same application 'user', the chances for having slave 'hits' are pretty high.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira