After further thought, I think (1) may be best for the following reasons:
a) In non-Fuse environments, generally an Elasticsearch cluster will use the default ports, and therefore using the default ports "out of the box" in non-Fuse environments is better from an administration perspective.
b) The intention is to manage ES nodes using Fuse profiles, so it should be easier to just set a different port when running with these profiles in Fuse. The administrator would then only need to change configuration, if those nodes needed to cluster with other nodes in the network that are using the standard port.
Hey Gary, going with option 1 might be the best idea until Fuse upgrade. Whats the reasoning behind the dated version?
- Does Fuse start a local data node or is it just client to connect to and external node.
-How does Duse expect to scale out their ES? by starting additional external ES data nodes or is it a case of starting an additional Fuse (Rtgov also need to answer this)
Some points to consider
- Fuse and RTgov need change some default setting so we don't get cluster cross talk.
- Cluster name
-Do we want multi cast enabled at all ?
Is there plans bring fuse to the latest version ?
Sorry for the late reply - didn't get a notification
Don't know the reason for the old version in fuse, or how they handle scale out - but agree these points need to be considered for rtgov in fuse.
Thanks for the pointers - will consider these when looking at how to start the server in fuse.