Dmitriy,
SystemD supports running multiple instances of one service – this is done through @-like syntax: 'sudo systemctl start apache-ignite@<configuration file name>', so that with every unique command string there will be started / stopped unique instance of Apache Ignite. And all instances can be restarted / stopped / enabled on boot / etc. simultaneously through 'sudo systemctl <command> apache-ignite@*'. Still, I can add a note about possibility of starting Apache Ignite manually through ignite.sh with a reference to corresponding documentation section, information where to look for the root of Apache Ignite installation and how to correctly start Apache Ignite in terms of permissions. File the documentation updates ticket? On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Petr, > > Most of the users will download and install Ignite so they can develop with > it. This means that they will be starting more than one node, which is > impossible if Ignite is a service. We should provide instructions to do > both. > > D. > > On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov <mr.wei...@gmail.com> wrote: > > > Dmitriy, > > > > > > Current packages design (both RPM and DEB) was reviewed and approved by > > community. I do not quite remember why service-based startup was chosen > but > > it seems rather logical and Unix-compliant – under Linux almost every > > service software is packed this way, which gives some benefits like > service > > autostart on reboot, centralized running nodes management (through > > systemctl), etc. There is no point in packing binary into Linux packages > if > > it then will be used as standalone executable. > > Yet, current design does not limit advanced user from running Apache > Ignite > > as standalone process – executing /usr/share/apache-ignite/bin/ignite.sh > > with parameters will start Apache Ignite node as if it was delivered by > > binary archive. > > > > > > > > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan <dsetrak...@apache.org> > > wrote: > > > > > Petr, > > > > > > Why do we even suggest starting Ignite as a service? Why not just start > > > Ignite instance as a stand-alone process? This should work, no? > > > > > > D. > > > > > > On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov <mr.wei...@gmail.com> > > wrote: > > > > > > > Unfortunately, it seems to be impossible (at least for now) — [1]. > > > > So we can say that current package design is for native Linux > > > installation > > > > only. > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8671? > > > > focusedCommentId=16496813&page=com.atlassian.jira. > > > > plugin.system.issuetabpanels:comment-tabpanel#comment-16496813 > > > > > > > > > > > > > On 31 May 2018, at 18:22, Petr Ivanov <mr.wei...@gmail.com> wrote: > > > > > > > > > > Filed https://issues.apache.org/jira/browse/IGNITE-8671 < > > > > https://issues.apache.org/jira/browse/IGNITE-8671> > > > > > > > > > > > > > > > > > > > >> On 31 May 2018, at 17:56, Dmitriy Setrakyan < > dsetrak...@apache.org > > > > <mailto:dsetrak...@apache.org>> wrote: > > > > >> > > > > >> On Thu, May 31, 2018 at 7:54 AM, Petr Ivanov <mr.wei...@gmail.com > > > > <mailto:mr.wei...@gmail.com>> wrote: > > > > >> > > > > >>> I’ll start the investigation. > > > > >>> > > > > >> > > > > >> Can you please file a ticket so we can track it? > > > > > > > > > > > > > > > > > > >
