From issues-return-47108-archive-asf-public=cust-asf.ponee.io@geode.apache.org Mon Feb 4 17:28:05 2019 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 5CA46180651 for ; Mon, 4 Feb 2019 18:28:05 +0100 (CET) Received: (qmail 905 invoked by uid 500); 4 Feb 2019 17:28:04 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 896 invoked by uid 99); 4 Feb 2019 17:28:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2019 17:28:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DA99C183CBD for ; Mon, 4 Feb 2019 17:28:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id LZTxMjcD8dZY for ; Mon, 4 Feb 2019 17:28:02 +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 E98BE6241E for ; Mon, 4 Feb 2019 17:28:01 +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 13DC3E26D8 for ; Mon, 4 Feb 2019 17:28:01 +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 833D124409 for ; Mon, 4 Feb 2019 17:28:00 +0000 (UTC) Date: Mon, 4 Feb 2019 17:28:00 +0000 (UTC) From: "Bruce Schuchardt (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (GEODE-4748) Geode put may result in inconsistent cache without SSL if network packets are tampered with 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/GEODE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-4748. ------------------------------------- Resolution: Won't Fix Geode already supplies SSL as a means to prevent packet-tampering. > Geode put may result in inconsistent cache without SSL if network packets are tampered with > ------------------------------------------------------------------------------------------- > > Key: GEODE-4748 > URL: https://issues.apache.org/jira/browse/GEODE-4748 > Project: Geode > Issue Type: Bug > Components: membership, serialization > Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0 > Reporter: Vadim Lotarev > Priority: Critical > Attachments: clumsy.jpg, geode-4748.log > > > Geode cache became inconsistent in case if networking and serialization problems occur at commit time. How to reproduce: > # create any simple _replicated_ region > # run two nodes > # put some value in the region (within a transaction or not) > # execute query on both nodes to check that the same value is returned (I used JMX for that) > # emulate somehow temporary networking or serialization error (throw IOException from toData() or use [clumsy|https://jagt.github.io/clumsy/] to emulate network interruption) > # repeat [#3], exception should occur > # repeat [#4] - you should see different values on different nodes > It looks like errors occurred after {{TXState.applyChanges}} produce inconsistency - it is impossible to rollback applied local changes what leads to the state where local cache contains changed data but other node(s) old data (before changes made in transaction). > To me, consistency is a key property for the systems like Geode so I would consider this bug as a critical one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)