ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Ignite Usability: Deadlocks and Starvation
Date Wed, 23 Aug 2017 23:32:01 GMT
Yakov,

I think as a first step, the deadlock detection should kick off after a
certain timeout, even if the transaction timeout was not set.

What do you think?

D.

On Wed, Aug 23, 2017 at 9:44 AM, Yakov Zhdanov <yzhdanov@apache.org> wrote:

> Hello, guys!
>
> Currently Ignite clusters are very vulnerable to deadlocks on tx and java
> levels and also thread pool starvation.
>
> Unfortunately, Ignite currently offers very poor functionality to protect
> and resolve situations of the kind.
>
> Here is the page with the info on this -
> https://cwiki.apache.org/confluence/display/IGNITE/Deadlock+Detection+And+
> Cluster+Protection
>
> Please provide comments here on dev list or on wiki. Then we will file
> tickets to plan these changes.
>
> --Yakov
>

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