From dev-return-32762-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Apr 2 10:06:14 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A23FA180627 for ; Mon, 2 Apr 2018 10:06:13 +0200 (CEST) Received: (qmail 25296 invoked by uid 500); 2 Apr 2018 08:06:12 -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 25281 invoked by uid 99); 2 Apr 2018 08:06:11 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2018 08:06:11 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 66CB4EB4F4; Mon, 2 Apr 2018 08:06:11 +0000 (UTC) From: alex-plekhanov To: dev@ignite.apache.org Reply-To: dev@ignite.apache.org Message-ID: Subject: [GitHub] ignite pull request #3729: IGNITE-8069 IgniteOutOfMemoryException should be ... Content-Type: text/plain Date: Mon, 2 Apr 2018 08:06:11 +0000 (UTC) GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3729 IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly … …to provided failure handler You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-8069 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3729.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3729 ---- commit fddeea5c509939e29dc126197e29cdcbc14bc33d Author: Aleksey Plekhanov Date: 2018-04-02T07:35:25Z IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly to provided failure handler ---- ---