From issues-return-28408-archive-asf-public=cust-asf.ponee.io@geode.apache.org Fri Jan 5 23:36:10 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 90FB5180647 for ; Fri, 5 Jan 2018 23:36:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 80D93160C15; Fri, 5 Jan 2018 22:36:10 +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 C6C77160C27 for ; Fri, 5 Jan 2018 23:36:09 +0100 (CET) Received: (qmail 34792 invoked by uid 500); 5 Jan 2018 22:36: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 34783 invoked by uid 99); 5 Jan 2018 22:36:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2018 22:36:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8A74B1A0AC0 for ; Fri, 5 Jan 2018 22:36:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id MVB7rSbDy1iK for ; Fri, 5 Jan 2018 22:36:02 +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 224AB5FB02 for ; Fri, 5 Jan 2018 22:36:02 +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 3791AE20C5 for ; Fri, 5 Jan 2018 22:36: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 7D18F24102 for ; Fri, 5 Jan 2018 22:36:00 +0000 (UTC) Date: Fri, 5 Jan 2018 22:36:00 +0000 (UTC) From: "Kirk Lund (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (GEODE-4180) Reference to locator view file and/or its contents are not cleaned up properly during cache close 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-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-4180: -------------------------------- Assignee: Kirk Lund > Reference to locator view file and/or its contents are not cleaned up properly during cache close > ------------------------------------------------------------------------------------------------- > > Key: GEODE-4180 > URL: https://issues.apache.org/jira/browse/GEODE-4180 > Project: Geode > Issue Type: Bug > Components: locator, tests > Affects Versions: 1.4.0 > Reporter: Kirk Lund > Assignee: Kirk Lund > > We temporarily set the member-timeout to max value to allow us to step through some code in the debugger. We noticed that if we run all 4 tests together, tests 2-3 were hanging. > After removing the member-timeout setting, we found that all of the tests after the 1st test are all trying to connect to the non-existent locator from the 1st test. This causes all tests after the 1st test to take ~2 seconds longer to run when run together than if you run them by individually. > After digging a bit more, I discovered that even though the test is deleting the entire directory containing the locator0view.dat file, some code somewhere must still have an open connection or stream to it because its contents from the 1st test continue to be read for each subsequent test even after the file itself and its directory have been deleted. > I believe some static code somewhere is keeping a reference to the file and/or its contents. So each test continues to read the same content even though the file no longer exists on disk. > The following shows the relevant messages logged by 4 tests in a DUnit test that shows tests 2-3 find and using the file and/or its contents from test 1. Note that I used IntelliJ debugger to confirm that this occurs even after test 1 deletes the file and its directory. > 1) createsRegionMappingOnceOnly > {noformat} > [vm0] [info 2017/12/29 10:59:30.826 PST tid=20] recovery file not found: /var/folders/28/m__9dv1906n60kmz7t71wm680000gn/T/junit543979839291182624/vm-0-createsRegionMappingOnceOnly/locator0view.dat > [vm0] [info 2017/12/29 10:59:31.135 PST tid=20] received new view: View[192.168.1.18(58582:locator):32770|0] members: [192.168.1.18(58582:locator):32770] > [vm0] old view is: null > {noformat} > 2) createsRegionMappingWithMinimumParams > {noformat} > [vm0] [info 2017/12/29 10:59:34.580 PST tid=20] Peer locator recovering from /var/folders/28/m__9dv1906n60kmz7t71wm680000gn/T/junit1076413749574999935/vm-0-createsRegionMappingWithMinimumParams/locator0view.dat > [vm0] [info 2017/12/29 10:59:34.580 PST tid=20] Peer locator recovered membership is View[192.168.1.18(58582:locator):32770|-1] members: [192.168.1.18(58580):32771{lead}] > {noformat} > 3) createsRegionMappingInService > {noformat} > [vm0] [info 2017/12/29 10:59:40.538 PST tid=20] Peer locator recovering from /var/folders/28/m__9dv1906n60kmz7t71wm680000gn/T/junit8253504123764665822/vm-0-createsRegionMappingInService/locator0view.dat > [vm0] [info 2017/12/29 10:59:40.538 PST tid=20] Peer locator recovered membership is View[192.168.1.18(58582:locator):32770|-1] members: [192.168.1.18(58580):32771{lead}] > {noformat} > 4) recreatesCacheFromClusterConfigWithRegionMapping > {noformat} > [vm0] [info 2017/12/29 10:59:46.495 PST tid=20] Peer locator recovering from /var/folders/28/m__9dv1906n60kmz7t71wm680000gn/T/junit1056719983598139185/vm-0-recreatesCacheFromClusterConfigWithRegionMapping/locator0view.dat > [vm0] [info 2017/12/29 10:59:46.496 PST tid=20] Peer locator recovered membership is View[192.168.1.18(58582:locator):32770|-1] members: [192.168.1.18(58580):32771{lead}] > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)