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 A333C200C3C for ; Mon, 3 Apr 2017 18:31:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A1DD6160B8D; Mon, 3 Apr 2017 16:31: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 F28AF160B9C for ; Mon, 3 Apr 2017 18:31:45 +0200 (CEST) Received: (qmail 22062 invoked by uid 500); 3 Apr 2017 16:31:45 -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 21926 invoked by uid 99); 3 Apr 2017 16:31:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2017 16:31:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 31584C023E for ; Mon, 3 Apr 2017 16:31:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id TbRta9vZckaa for ; Mon, 3 Apr 2017 16:31:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D22AD61E21 for ; Mon, 3 Apr 2017 16:31:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4E188E0BCD for ; Mon, 3 Apr 2017 16:31:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AB48F2401C for ; Mon, 3 Apr 2017 16:31:41 +0000 (UTC) Date: Mon, 3 Apr 2017 16:31:41 +0000 (UTC) From: "Alexander Menshikov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture() MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 03 Apr 2017 16:31:46 -0000 [ https://issues.apache.org/jira/browse/IGNITE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953742#comment-15953742 ] Alexander Menshikov edited comment on IGNITE-1948 at 4/3/17 4:31 PM: --------------------------------------------------------------------- [~sboikov] Okay I total recalled :) In PR I use only checked exception. It's unclear for me how reach both aims: ensure retry future not null and not create new exception class. Do you mean make some default not null value for retry future? was (Author: sharpler): [~sboikov] Okay I total recalled :) In PR I use only checked exception. It's not clear for me how reach both: ensure retry future not null and don't create new exception class. Do you mean make some default not null value for retry future? > ClusterTopologyCheckedException can return null for retryReadyFuture() > ---------------------------------------------------------------------- > > Key: IGNITE-1948 > URL: https://issues.apache.org/jira/browse/IGNITE-1948 > Project: Ignite > Issue Type: Bug > Components: general > Reporter: Denis Magda > Assignee: Alexander Menshikov > Fix For: 2.0 > > > It was noted that {{ClusterTopologyCheckedException}} ready future can be null. > Go though all the places where this kind of exception is being initialized and check why the ready future is not set in some cases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)