From dev-return-80493-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Fri Apr 26 21:46:03 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 68CB218064C for ; Fri, 26 Apr 2019 23:46:03 +0200 (CEST) Received: (qmail 39670 invoked by uid 500); 26 Apr 2019 21:46:02 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 39659 invoked by uid 99); 26 Apr 2019 21:46:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2019 21:46:02 +0000 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 6036AE2B49 for ; Fri, 26 Apr 2019 21:46: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 7405025818 for ; Fri, 26 Apr 2019 21:46:00 +0000 (UTC) Date: Fri, 26 Apr 2019 21:46:00 +0000 (UTC) From: "Shawn Heisey (JIRA)" To: dev@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ZOOKEEPER-2348) Data between leader and followers are not synchronized. 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/ZOOKEEPER-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827338#comment-16827338 ] Shawn Heisey commented on ZOOKEEPER-2348: ----------------------------------------- Does this problem affect 3.4.x versions, or just 3.5.x? A problem is being discussed on the solr-user mailing list and we're trying to figure out whether this bug could be involved. The referenced version of Solr (7.7.1) includes ZK 3.4.13. > Data between leader and followers are not synchronized. > ------------------------------------------------------- > > Key: ZOOKEEPER-2348 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2348 > Project: ZooKeeper > Issue Type: Bug > Affects Versions: 3.5.1 > Reporter: Echo Chen > Priority: Major > > When client session expired, leader tried to remove it from session map and remove its EPHEMERAL znode, for example, /test_znode. This operation succeed on leader, but at the very same time, network fault happended and not synced to followers, a new leader election launched. After leader election finished, the new leader is not the old leader. we found the znode /test_znode still existed in the followers but not on leader > *Scenario :* > 1) Create znode E.g. > {{/rmstore/ZKRMStateRoot/RMAppRoot/application_1449644945944_0001/appattempt_1449644945944_0001_000001}} > 2) Delete Znode. > 3) Network fault b/w follower and leader machines > 4) leader election again and follower became leader. > Now data is not synced with new leader..After this client is not able to same znode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)