ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Kuznetsov <stku...@gmail.com>
Subject Re: Ignite Usability: Deadlocks and Starvation
Date Wed, 23 Aug 2017 19:18:00 GMT
Hi folks,

Strictly speaking, it's not about improving deadlock/starvation detection
mechanisms, but how do we handle fragile concurrent code that (potentially)
leads to this kind of issues? For example, what if the method is assumed to
be thread-safe, but its safety depends on arguments supplied?

2017-08-23 19:44 GMT+03:00 Yakov Zhdanov <yzhdanov@apache.org>:

> 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

Best regards,
  Andrey Kuznetsov.

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