Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 62CD1200CFC for ; Thu, 24 Aug 2017 01:32:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5F2CB169324; Wed, 23 Aug 2017 23:32:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CC458166708 for ; Thu, 24 Aug 2017 01:32:45 +0200 (CEST) Received: (qmail 27169 invoked by uid 500); 23 Aug 2017 23:32:44 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 27158 invoked by uid 99); 23 Aug 2017 23:32:44 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2017 23:32:44 +0000 Received: from mail-qt0-f170.google.com (mail-qt0-f170.google.com [209.85.216.170]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id B4D5B1A002B for ; Wed, 23 Aug 2017 23:32:43 +0000 (UTC) Received: by mail-qt0-f170.google.com with SMTP id d15so8334040qta.0 for ; Wed, 23 Aug 2017 16:32:42 -0700 (PDT) X-Gm-Message-State: AHYfb5gVg2SsB8rtpSmPKlvbNoVEwUbCPM7mY3lZeLq10r1B/INMTWml dfK39CyMuk7DbzOAIae5Gj8gzwRk5yHl X-Received: by 10.237.35.179 with SMTP id j48mr5796561qtc.59.1503531162165; Wed, 23 Aug 2017 16:32:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.34.6 with HTTP; Wed, 23 Aug 2017 16:32:01 -0700 (PDT) In-Reply-To: References: From: Dmitriy Setrakyan Date: Wed, 23 Aug 2017 16:32:01 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Ignite Usability: Deadlocks and Starvation To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="001a113771bad47d3105577420be" archived-at: Wed, 23 Aug 2017 23:32:46 -0000 --001a113771bad47d3105577420be Content-Type: text/plain; charset="UTF-8" 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 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 > --001a113771bad47d3105577420be--