[
https://issues.apache.org/jira/browse/AMBARI-21475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Phipps updated AMBARI-21475:
--------------------------------
Description:
Hi,
It appears the Elasticsearch plugin can't recognise the responses from the new
systemd service control messages, as despite the logs showing the service has
been stopped successfully, the task is failing in the Ambari UI.
Elasticsearch plugin version 2.3.3
Log:
!es-stop-fail.png|large!
Thanks,
Rob
was:
Hi,
It appears the Elasticsearch plugin can't recognise the responses from the new
systemd service control messages, as despite the logs showing the service has
been stopped successfully, the task is failing in the Ambari UI.
Elasticsearch plugin:
!es-ver.png|thumbnail!
Log:
!es-stop-fail.png|thumbnail!
Thanks,
Rob
> Elasticsearch systemd support
> -----------------------------
>
> Key: AMBARI-21475
> URL: https://issues.apache.org/jira/browse/AMBARI-21475
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.3
> Environment: CentOS 7 x64
> Reporter: Rob Phipps
> Attachments: es-stop-fail.png
>
>
> Hi,
> It appears the Elasticsearch plugin can't recognise the responses from the
> new systemd service control messages, as despite the logs showing the service
> has been stopped successfully, the task is failing in the Ambari UI.
> Elasticsearch plugin version 2.3.3
> Log:
> !es-stop-fail.png|large!
> Thanks,
> Rob
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)