Viya 3.5 ARK MMSU creates duplicate Elastic Search processes when starting servies

[yuvraj-sysengai]

Environment details :

Ansible Version - ansible-core 2.15.12
Python version - 3.9.16
OS Version - Red Hat Enterprise Linux 7.9
Viya-ark version -Viya35-ark-1.21

Issue :

When starting services using viya-ark ansible scripts, two Elasticsearch processes are created which causes memory usage to reach around 90%.
However when services are started using systemctl , only one Elasticsaerch process starts and the environment works normally.

Please confirm if this is a known issue with viya-ark and advise if there is any fix or workaround.

[kevinlinglesas]

@yuvraj-sysengai can you provide some additional information, please?

1. What is your Viya 3 deployment topology? (single or multi-machine)
2. What version of Viya 3 are you deploying?
3. What other services are also running on the same host as elastic process(es)? (if multi-machine env)
4. Can you provide viya-services-status.ym playbook output that includes the 2 Elasticsearch processes started?
5. How exactly are you invoking viya-mmsu playbooks? (so we might run the same)
6. What exact systemctl commands are you running? (so we might run the same)

Thank you.