Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 99E1E17383 for ; Thu, 3 Mar 2016 02:31:18 +0000 (UTC) Received: (qmail 15980 invoked by uid 500); 3 Mar 2016 02:31:18 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 15777 invoked by uid 500); 3 Mar 2016 02:31:18 -0000 Mailing-List: contact issues-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 issues@ignite.apache.org Received: (qmail 15557 invoked by uid 99); 3 Mar 2016 02:31:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Mar 2016 02:31:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 217742C1F5D for ; Thu, 3 Mar 2016 02:31:18 +0000 (UTC) Date: Thu, 3 Mar 2016 02:31:18 +0000 (UTC) From: "Alexey Goncharuk (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (IGNITE-257) Revisit heuristic transaction failure handling MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk closed IGNITE-257. ----------------------------------- > Revisit heuristic transaction failure handling > ---------------------------------------------- > > Key: IGNITE-257 > URL: https://issues.apache.org/jira/browse/IGNITE-257 > Project: Ignite > Issue Type: Sub-task > Components: cache > Affects Versions: 1.1.4 > Reporter: Alexey Goncharuk > Assignee: Alexey Goncharuk > Fix For: 1.6 > > > Current tests assume that all transaction entries are invalidated, even though it is not always possible. Need to revisit heuristic exception handling logic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)