Peter, can you please fix the text below to point to "log", not "lib"?

log directory is at /var/lib/apache-ignite (mapped to
> /var/lib/apache-ignite/log)


On Mon, Jun 4, 2018 at 7:07 AM, Petr Ivanov <mr.wei...@gmail.com> wrote:

> Log directory is directly at /var/log/apache-ignite and mapped via symlink
> to /var/lib/apache-ignite/log because /var/lib/apache-ignite/ (main work
> dir which in its turn is mapped via symlink to
> /usr/share/apache—ignite/work) is the place where running node of Apache
> Ignite will write it’s logs.
>
>
>
> > On 4 Jun 2018, at 16:56, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
> >
> > Thanks, Petr!
> >
> > I think the log directory should be at /var/log, not /var/lib, right?
> >
> > D.
> >
> > On Mon, Jun 4, 2018 at 5:04 AM, Petr Ivanov <mr.wei...@gmail.com> wrote:
> >
> >> Dmitriy,
> >>
> >>
> >> I’ve added requested information (see [1]).
> >> Can you check that this information is enough, please?
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-8671?focusedCom
> >> mentId=16500123&page=com.atlassian.jira.plugin.system.
> >> issuetabpanels:comment-tabpanel#comment-16500123
> >>
> >>
> >>
> >>
> >>> On 3 Jun 2018, at 10:24, Dmitriy Setrakyan <dsetrak...@apache.org>
> >> wrote:
> >>>
> >>> Peter,
> >>>
> >>> I think what is really missing is the installation structure, i.e.
> where
> >> is
> >>> the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere
> as
> >> a
> >>> result of the installation? I think, if you explain it to users, there
> >> will
> >>> be more understanding from the user stand point.
> >>>
> >>> Can you please add that?
> >>>
> >>> D.
> >>>
> >>> On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov <mr.wei...@gmail.com>
> >> wrote:
> >>>
> >>>> Dmitriy,
> >>>>
> >>>>
> >>>> I've added warning snippet in the bottom of the Alternative
> Installation
> >>>> Options section with reference on how to start Apache Ignite installed
> >> from
> >>>> RPM or DEB packages as standalone Java application (see [1]).
> >>>> Hope it will be enough.
> >>>>
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
> >>>> focusedCommentId=16499157&page=com.atlassian.jira.
> >>>> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> On 2 Jun 2018, at 21:57, Dmitriy Setrakyan <dsetrak...@apache.org>
> >>>> wrote:
> >>>>>
> >>>>> Peter,
> >>>>>
> >>>>> We cannot have a distribution that works sometimes.
> >>>>>
> >>>>> I think you should read the ticket carefully. I don't beleive we need
> >> to
> >>>>> make any changes to the release, it is a matter of fixing the
> >>>>> documentation.
> >>>>>
> >>>>> Can you confirm this?
> >>>>>
> >>>>> D.
> >>>>>
> >>>>>
> >>>>> On Jun 2, 2018 11:44, "Peter Ivanov" <mr.wei...@gmail.com> wrote:
> >>>>>
> >>>>> Dmitriy,
> >>>>>
> >>>>>
> >>>>> You suggest removing fully working under corresponding Linux
> >> distributive
> >>>>> RPM and DEB packages entirely from apache.org/dist/ignite only
> because
> >>>> they
> >>>>> do not work in highly unlikely scenario (Windows 10 WSL) as service?
> >>>>>
> >>>>> I will certainly add reference about running Apache Ignite from the
> >>>>> packages as standalone Java application (with corresponding
> permissions
> >>>>> note) but I’d like to hear community opinion on the whole matter -
> >>>>> everything that was done, was done with review and approve from lots
> of
> >>>>> Apache Ignite commiters and PMCs, including PMC chair.
> >>>>>
> >>>>>
> >>>>> On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> >>>>> wrote:
> >>>>>
> >>>>>
> >>>>>> Peter,
> >>>>>>
> >>>>>> I have reopened this ticket:
> >>>>>> https://issues.apache.org/jira/browse/IGNITE-8671
> >>>>>>
> >>>>>> I changed the priority to blocker. At this point I suggest the
> >>>> following:
> >>>>>> - we either remove the DEB and RPM packages from the website and
> >> readme
> >>>>>> - or we fix this issue ASAP as stated in the ticket.
> >>>>>>
> >>>>>> I will leave it up to you to decide.
> >>>>>>
> >>>>>> D.
> >>>>>>
> >>>>>> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov <mr.wei...@gmail.com
> >
> >>>>>> wrote:
> >>>>>>
> >>>>>>> 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?
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>

Reply via email to