[teiid-issues] [JBoss JIRA] (TEIID-2169) Buffer Manger's memory should be backed by Infinispan Cache

Tue Apr 16 14:57:53 EDT 2013

     [ https://issues.jboss.org/browse/TEIID-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-2169:
----------------------------------

    Fix Version/s:     (was: 8.4)

Pulling out of 8.4 based upon the last comment as it would take some time for the necessary mechanisms to become available in Infinispan.  

A separate issue is how to handle mat view replication - if that is something we want do more via a different integration (for example modeshape) or modify our table logic to allow for page based replication and direct usage of infinispan rather than our current low level replication approach.

> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira