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 1881B200C48 for ; Thu, 6 Apr 2017 12:55:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 17335160B84; Thu, 6 Apr 2017 10:55:47 +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 5E631160B83 for ; Thu, 6 Apr 2017 12:55:46 +0200 (CEST) Received: (qmail 10768 invoked by uid 500); 6 Apr 2017 10:55: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 10759 invoked by uid 99); 6 Apr 2017 10:55:45 -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; Thu, 06 Apr 2017 10:55:45 +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 3FDE5C05E9 for ; Thu, 6 Apr 2017 10:55:45 +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-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Cq6uttWCF7-D for ; Thu, 6 Apr 2017 10:55:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id CCEA75FACA for ; Thu, 6 Apr 2017 10:55:43 +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 C25C7E0D22 for ; Thu, 6 Apr 2017 10:55: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 ED2522407D for ; Thu, 6 Apr 2017 10:55:41 +0000 (UTC) Date: Thu, 6 Apr 2017 10:55:41 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-2722) Inconsistent "keepBinary" flag propagation for EVT_CACHE_REBALANCE_OBJECT_LOADED event. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 06 Apr 2017 10:55:47 -0000 [ https://issues.apache.org/jira/browse/IGNITE-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2722: ------------------------------------ Fix Version/s: (was: 2.0) 2.1 > Inconsistent "keepBinary" flag propagation for EVT_CACHE_REBALANCE_OBJECT_LOADED event. > --------------------------------------------------------------------------------------- > > Key: IGNITE-2722 > URL: https://issues.apache.org/jira/browse/IGNITE-2722 > Project: Ignite > Issue Type: Bug > Components: cache > Affects Versions: 1.5.0.final > Reporter: Vladimir Ozerov > Fix For: 2.1 > > > I searched through usages of EVT_CACHE_REBALANCE_OBJECT_LOADED event and noticed that we pass different value of "keepBinary" flag in different situations: > 1) {{GridDhtLockFuture.MiniFuture.onResult}} - false > 2) {{GridDhtTxPrepareFuture.MiniFuture.onResult}} - false > 2) {{GridDhtForceKeysFuture.MiniFuture.onResult}} - false > 4) {{GridDhtPartitionDemander.preloadEntry}} - true > Looks like with this approach user is not able to use corresponding event listener normally because he will receive both serialized and de-serialized objects. > As I understand, we must always pass {{true}} here because we do not know whether node has corresponding classes or not. > Other rebalance events must be reviewed as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)