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 8D5F9200CCC for ; Fri, 21 Jul 2017 12:51:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8A50D16D046; Fri, 21 Jul 2017 10:51:05 +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 D097716D045 for ; Fri, 21 Jul 2017 12:51:04 +0200 (CEST) Received: (qmail 16643 invoked by uid 500); 21 Jul 2017 10:51:03 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 16632 invoked by uid 99); 21 Jul 2017 10:51:03 -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; Fri, 21 Jul 2017 10:51:03 +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 7310C180633 for ; Fri, 21 Jul 2017 10:51:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id a7dV8SaLuszn for ; Fri, 21 Jul 2017 10:51: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 0BE145FB8D for ; Fri, 21 Jul 2017 10:51: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 BCFEBE0DF0 for ; Fri, 21 Jul 2017 10:51:00 +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 1F8D521EE9 for ; Fri, 21 Jul 2017 10:51:00 +0000 (UTC) Date: Fri, 21 Jul 2017 10:51:00 +0000 (UTC) From: "Vikas Vishwakarma (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (PHOENIX-4044) Orphaned chunk of 15650000 bytes found during finalize MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 21 Jul 2017 10:51:05 -0000 Vikas Vishwakarma created PHOENIX-4044: ------------------------------------------ Summary: Orphaned chunk of 15650000 bytes found during finalize Key: PHOENIX-4044 URL: https://issues.apache.org/jira/browse/PHOENIX-4044 Project: Phoenix Issue Type: Bug Affects Versions: 4.10.0 Reporter: Vikas Vishwakarma Priority: Minor Observing these WARNINGS in the RegionServer logs similar to what is discussed PHOENIX-1011 2017-07-20 10:10:00,421 WARN [Finalizer] memory.GlobalMemoryManager - Orphaned chunk of 15650000 bytes found during finalize 2017-07-20 10:10:00,421 WARN [Finalizer] memory.GlobalMemoryManager - Orphaned chunk of 15650000 bytes found during finalize 2017-07-20 10:10:21,153 WARN [Finalizer] memory.GlobalMemoryManager - Orphaned chunk of 15650000 bytes found during finalize I am not able to identify the exact sequence of events that lead to these warnings but the scenario we were testing is as follows: We were trying to simulate Index update failures for one of our tests to check index rebuild scenario For this we did a close_region on one of the index table regions so that all updates on this region will fail with NSRE With this we start seeing index update failures, scanner lease expiries, etc After sometime we re-assign the closed_region to trigger index rebuild We start seeing these WARNING messages related to Orphaned chunks in Regionserver logs in this case -- This message was sent by Atlassian JIRA (v6.4.14#64029)