We introduced a custom systemd unit for elasticsearch as we need some specifics for multi-instance to work. This causes some issues, in particular because this custom unit name isn't stable (it contains ${version}). A better solution would be to use a systemd override, which is exposed by puppet base::service_unit since T143210. There might be some gotcha, so reading T143210 before starting implementation is required.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| elasticsearch: remove from systemd unit | operations/puppet | production | +7 -7 |
Related Objects
Related Objects
Event Timeline
Comment Actions
actually, we're deploying a new unit as a template, so I'm not sure if we can just override the standard one. This will need discussion with someone who understand systemd better than I do.
Comment Actions
Change 497503 had a related patch set uploaded (by Mathew.onipe; owner: Mathew.onipe):
[operations/puppet@production] elasticsearch: remove from systemd unit
Comment Actions
Change 497503 abandoned by Ryan Kemper:
[operations/puppet@production] elasticsearch: remove from systemd unit
Reason: