Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CALUCNEtoNCDR=1Sbe3c06tRw=VCm54jmx75O5kPXBUyR=OjTtw@mail.gmail.com>
References: <CADM=oMYLL6pPtxx-rT+rmOmb6ckygT_qD9VXu-TdQVX38Egw+Q@mail.gmail.com>
 <CALUCNEtoNCDR=1Sbe3c06tRw=VCm54jmx75O5kPXBUyR=OjTtw@mail.gmail.com>
From: Anton Vinogradov <av@apache.org>
Date: Fri, 8 Sep 2017 17:15:25 +0300
Message-ID: <CAOKDqC8ot074BbJG60-PEe+3e+YwTHfNRk13KOrTK5BqDeAtEg@mail.gmail.com>
Subject: Re: Monitoring of active transactions
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="089e082693785b39f70558ae35f9"
archived-at: Fri, 08 Sep 2017 14:15:32 -0000

--089e082693785b39f70558ae35f9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Ilya,

We extremely need this!

Txs and Locks info should be collected on each cluster hang.
We already have an issue related to this problem -
https://issues.apache.org/jira/browse/IGNITE-4937

Nikolay,

Good point,
but, seems you should start separate thread to discuss this.

On Fri, Sep 8, 2017 at 4:28 PM, Dmitry Pavlov <dpavlov.spb@gmail.com> wrote=
:

> Hi Ilya,
>
> I'm definitely +1 for including the utility in the product. Perfect
> contribution.
>
> Sincerely,
> Dmitriy Pavlov
>
> =D0=BF=D1=82, 8 =D1=81=D0=B5=D0=BD=D1=82. 2017 =D0=B3. =D0=B2 14:28, Ilya=
 Lantukh <ilantukh@gridgain.com>:
>
> > Igniters,
> >
> > According to our current design and implementation, unclosed transactio=
n
> or
> > unreleased lock can hang ignite cluster forever. This is logical, and
> with
> > correct usage of those mechanics such issue should never happen, in rea=
l
> > world developers can make mistakes and leave transaction open. We have =
a
> > feature "transaction timeout", but turns out it doesn't work in all cas=
es
> > (see https://issues.apache.org/jira/browse/IGNITE-6181). Even if all
> known
> > issues are fixed, there is still a lot of room for mistake and incorrec=
t
> > usage.
> >
> > To make it possible for Ignite users to discover such problem and trace
> it
> > to a particular part of code, I've created a very simple utility that
> > collects and prints information about long running transactions for the
> > whole cluster. It is available here:
> > https://github.com/ilantukh/IgniteTxViewer.
> >
> > One might expect such monitoring utilities to be included in Ignite
> > codebase. Personally, I think that such information should be available
> > from public API, without using of additional applications or diving int=
o
> > Ignite internals.
> >
> > What do you think?
> >
> > --
> > Best regards,
> > Ilya
> >
>

--089e082693785b39f70558ae35f9--