[
https://jira.jboss.org/browse/TEIID-1104?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy commented on TEIID-1104:
-------------------------------------
SteveH's comment
1. Engine clustering - security/caching
2. Administrative clustering - what operations need to be across the whole cluster at
runtime?
3. Configuration clustering - what needs to be done to ensure deployed artifacts and
bindings for JNDI/security are distributed across the cluster
Half of #1 is already being handled through caching issues. There was also not much
response to a dev posting on how we'll deal with sessioning, so I'll make the call
there also and create the appropriate JIRA.
#2 really only comes into play if there's something that we wish to appear global but
is still a per instance operation. Tooling could compensate, but my hope would be that
all caches, user sessions, etc. will be effectively global.
Finally, the belief has been that AS will handle the artifact replication for #3. I'm
a bit fuzzy though on how the JNDI/security bindings will work in clustered mode.
Teiid engine will be clusterable.
---------------------------------
Key: TEIID-1104
URL:
https://jira.jboss.org/browse/TEIID-1104
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Van Halbert
Fix For: 7.1
The Teiid engine must support the ability to be clustered.
--
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