[teiid-issues] [JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492150#comment-13492150 ] 

Steven Hawkins commented on TEIID-5007:
---------------------------------------

> Also AFAIK in Openshift Wildfly works with stand alone-ha mode only not domain

Yes, the entry point has logic to support domain, but that is for generic docker usage not OS.

>  Thus you may be seeing the difference in configuration for JDG

What I mean is that in other configurations, such as https://github.com/fabric8io/fabric8-infinispan-docker/blob/f0b56e9aff5f951be72d6091eb4f8851f6f5b4df/src/main/resources/standalone/configuration/clustered.xml#L172
or 
https://github.com/infinispan/infinispan-openshift-templates/blob/4081c10f2bd3196aaf34c2bc45e94c1e20633b18/configurations/cloud-ephemeral.xml#L217
The configuration is specific to the infinispan jgroups.  Infinispan is also having to pass in additional information about the default stack, and in older iterations had additional steps - https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_for_openshift/3/single/red_hat_jboss_data_grid_for_openshift/index#jdg-clustering


> 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)