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 CE9F7200CC6 for ; Tue, 18 Jul 2017 08:45:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CD1F716666A; Tue, 18 Jul 2017 06:45: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 21770166664 for ; Tue, 18 Jul 2017 08:45:04 +0200 (CEST) Received: (qmail 68010 invoked by uid 500); 18 Jul 2017 06:45:04 -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 67999 invoked by uid 99); 18 Jul 2017 06:45:04 -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; Tue, 18 Jul 2017 06:45:04 +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 B59631A0933 for ; Tue, 18 Jul 2017 06:45:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-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 46nkSWlZtc-8 for ; Tue, 18 Jul 2017 06:45:03 +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 6878A60D92 for ; Tue, 18 Jul 2017 06:45: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 38082E0E0F for ; Tue, 18 Jul 2017 06:45: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 6917F2476C for ; Tue, 18 Jul 2017 06:45:00 +0000 (UTC) Date: Tue, 18 Jul 2017 06:45:00 +0000 (UTC) From: "Ankit Singhal (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-4033) Limit number of rows instead of time period for partial index rebuilder MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 18 Jul 2017 06:45:06 -0000 [ https://issues.apache.org/jira/browse/PHOENIX-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091195#comment-16091195 ] Ankit Singhal commented on PHOENIX-4033: ---------------------------------------- yeah, the goal was to do the rebuild the indexes in the batches with the checkpointing so that we don't usually time out, also give chance to other indexes and will not lose the work done for the large rebuild when region server holding SYSTEM.CATALOG restarted. I think, we can't use PageFilter as we don't know from which point we should start for the next batch. > Limit number of rows instead of time period for partial index rebuilder > ----------------------------------------------------------------------- > > Key: PHOENIX-4033 > URL: https://issues.apache.org/jira/browse/PHOENIX-4033 > Project: Phoenix > Issue Type: Bug > Reporter: James Taylor > > There's a mechanism in MetaDataRegionObserver to limit the time period of the partial index rebuilder (based on QueryServices.INDEX_FAILURE_HANDLING_REBUILD_PERIOD). Assuming the goal is to limit the number of rows being processed during one scan, we should push a PageFilter instead, since limiting the time period may not limit the number of rows processed at a time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)