[
https://issues.apache.org/jira/browse/IGNITE-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448422#comment-16448422
]
Max Shonichev commented on IGNITE-7108:
---------------------------------------
It seems a little inconvenient to me that user must always put config filename
to perform any operation with service.
basic use case: admin wants to quickly check status of service
{noformat}
# systemctl status apache-ignite
● apache-ignite.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
{noformat}
Wow-wow, why is it dead? It is actually not, but you'd asked it wrong:
{noformat}
# systemctl status [email protected]
● [email protected] - Apache Ignite In-Memory Computing
Platform Service
Loaded: loaded (/etc/systemd/system/[email protected]; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2018-04-23 16:23:26 UTC; 14min ago
Process: 69 ExecStart=/usr/share/apache-ignite/bin/service.sh start %i
(code=exited, status=0/SUCCESS)
Process: 67 ExecStartPre=/usr/bin/env bash
/usr/share/apache-ignite/bin/service.sh set-firewall (code=exited,
status=0/SUCCESS)
Process: 66 ExecStartPre=/bin/chown ignite:ignite /var/run/apache-ignite
(code=exited, status=0/SUCCESS)
Process: 65 ExecStartPre=/bin/mkdir /var/run/apache-ignite (code=exited,
status=0/SUCCESS)
Main PID: 70 (ignite.sh)
CGroup:
/docker/a198605103cc6e6b20ac411ed8b3c80d5f669e5dedd23e03c60bb71a355ebe1a/system.slice/system-apache\x2dignite.slice/[email protected]
├─ 70 /bin/bash /usr/share/apache-ignite/bin/ignite.sh
/etc/apache-ignite/default-config.xml
└─165 /usr/bin/java -Xms1g -Xmx1g -server -XX:+AggressiveOpts
-XX:MaxMetaspaceSize=256m -DIGNITE_QUIET=true
-DIGNITE_SUCCESS_FILE=/usr/share/apache-ignite/work/ignit
e_success_1d84d0dc-b239-4449-adae-5800891b9765 -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=49112
-Dcom.sun.management.jmxremote.authenticate=false -Dco
m.sun.management.jmxremote.ssl=false -DIGNITE_HOME=/usr/share/apache-ignite
-DIGNITE_PROG_NAME=/usr/share/apache-ignite/bin/ignite.sh -cp
/usr/share/apache-ignite/libs/*:/usr
/share/apache-ignite/libs/ignite-indexing/*:/usr/share/apache-ignite/libs/ignite-spring/*:/usr/share/apache-ignite/libs/licenses/*
org.apache.ignite.startup.cmdline.CommandLi
neStartup /etc/apache-ignite/default-config.xml
Apr 23 16:23:26 a198605103cc systemd[1]: Starting Apache Ignite In-Memory
Computing Platform Service...
Apr 23 16:23:26 a198605103cc systemd[1]: Started Apache Ignite In-Memory
Computing Platform Service.
{noformat}
Is it possible to at least dump for which configs are nodes started if they
are?
Also, when node is stopped/crashed we could scratch a head forever before we
get an understanding from which config should we restart it again.
Very awkward, IMO.
> Apache Ignite 2.5 RPM and DEB packages
> --------------------------------------
>
> Key: IGNITE-7108
> URL: https://issues.apache.org/jira/browse/IGNITE-7108
> Project: Ignite
> Issue Type: New Feature
> Components: binary
> Reporter: Peter Ivanov
> Assignee: Peter Ivanov
> Priority: Critical
> Labels: important
> Fix For: 2.5
>
>
> # (/) Update RPM build process to unify with DEB build.
> # (/) Prepare build of DEB package (using architecture and layout from RPM
> package).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
