[
https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin....
]
ivan mckinley commented on RTGOV-462:
-------------------------------------
1) If we are starting a full server for production use, this would also require the full
stack, wouldn't it? So this would be the same for both production and test/integration
requirements?
- correct. but perhaps in remote client mode there will be no need to pull in the full
stack
2) Singleton - yes, although the ElasticsearchClient is not a singleton, it could manage a
'singleton' for the embedded server, in cases where the specific
ElasticsearchClient instance has referenced it (or possibly where the host is
unspecified).
If the embedded node's config is obtained from the overlord-rtgov.properties, this
should enable clustering to be supported/updated as appropriate, without impacting the
individual components using ES.
Unique config per instance - this could be more complex. It may be possible via the
overlord-rtgov.properties when running in standalone mode, but (as I understand it) when
we use domain mode, this info will be obtained from the xml - which will be common across
a cluster of servers (I assume). So we may need the embedded nodes (in this scenario) to
use a common general config, and potentially the more specific config is applied to ES
nodes outside of EAP?
Perhaps the best approach in the this case would be.
-
Domain mode. All ES nodes form a cluster based on config in xml(assumption). ES
Configuration by default. Perhaps taking config from EAP clustering(if clustering in use).
if another ES cluster or shard is required then a separate domain could be defined. what
do you think?
- Standalone. Flexible configuration using RTGov.properties. This is straight forward.
Explore whether ElasticSearch server can be embedded into container
(EAP)
-------------------------------------------------------------------------
Key: RTGOV-462
URL:
https://issues.jboss.org/browse/RTGOV-462
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: ivan mckinley
Fix For: 2.0.0.Final
Original Estimate: 1 week
Remaining Estimate: 1 week
Determine whether ElasticSearch could be embedded within EAP/Karaf.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)