ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anton Vinogradov ...@apache.org>
Subject Re: Monitoring of active transactions
Date Fri, 08 Sep 2017 14:15:25 GMT
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
>
> пт, 8 сент. 2017 г. в 14:28, Ilya Lantukh <ilantukh@gridgain.com>:
>
> > Igniters,
> >
> > According to our current design and implementation, unclosed transaction
> or
> > unreleased lock can hang ignite cluster forever. This is logical, and
> with
> > correct usage of those mechanics such issue should never happen, in real
> > world developers can make mistakes and leave transaction open. We have a
> > feature "transaction timeout", but turns out it doesn't work in all cases
> > (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 incorrect
> > 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 into
> > Ignite internals.
> >
> > What do you think?
> >
> > --
> > Best regards,
> > Ilya
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message