[
https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5007:
-------------------------------------
What I know is that JGroups default protocol like MPING does not work in OpenShift. So,
they have come with KUBE PING protocol for JGroups. But do not know any more details. The
default standalone.xml in Openshift image is stanndalone-openshift.xml file, see if there
are config information.
Also, see in JDG shared cache service configuration, that is based on WildFly too, they
must be clustered JGroups there too.
Changes to reduce Teiid in the cloud footprint
----------------------------------------------
Key: TEIID-5007
URL:
https://issues.jboss.org/browse/TEIID-5007
Project: Teiid
Issue Type: Quality Risk
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.1
A Teiid instance even as swarm or springboot needs additional considerations to minimize
the runtime footprint. This includes:
* container aware auto-sizing. Detection of the number of cpus and available memory need
refined - there are experimental settings being considered for containerized vms to better
report these values and there is logic in WildFly and other projects that attempts better
auto-detection. We also need to utilize the memory buffer space more and probably as
off-heap space (and ideally direct operations on the serialized data)
* Subsystems required include JTA, webserver, security, which could be satisfied by
slimmer alternative versions - especially if we make new assumptions, such as not
utilizing xa transactions.
* Engine dependencies could be application specific - removing xml/xsl support, geometry
support, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)