[
https://issues.jboss.org/browse/TEIID-2169?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2169:
---------------------------------------
The primary goal is not session failover. Without lots of driver support and/or an
extreme amount of server side work TAF (transparent application failover) will not be
realized. Issues include process plan serialization, session scoped temp tables,
transaction resumption, re-establishing cursor positions, session state replication, etc.
We're really initially just interested in replacing the LFRU memory/memory buffer
eviction logic with local infinispan caches that still handle the eviction strategy with
the Teiid logic (object->memory buffer->disk). This memory buffer, beyond allowing
direct memory access, also allows us to appropriately bucket the file entries to avoid
file fragmentation.
Buffer Manger's memory should be backed by Infinispan Cache
-----------------------------------------------------------
Key: TEIID-2169
URL:
https://issues.jboss.org/browse/TEIID-2169
Project: Teiid
Issue Type: Feature Request
Components: Query Engine, Server
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Currently the buffer manager uses the memory from the local VM's heap for processing
the intermediate query results, anything that overruns is saved on the disk. Using this
model so far proven very efficient.
However, when it comes to using the data grid as unlimited temp backing store where the
results can be shared with other nodes in the case of fail-over of the session, this in
current model does not work. By using the infinispan's local cache in standalone and
replicated cache in distributed node for the buffer manager these issues can resolved.
Issues may be, currently Buffer Manager uses efficient btree based index store, also the
uses file storage in block. To make it work, Teiid needs to have access to the
Infinispan's eviction queue and may also needs to implement the cache store.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira