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 EE64E200D1C for ; Sun, 1 Oct 2017 08:17:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E34E51609EE; Sun, 1 Oct 2017 06:17: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 334131609D5 for ; Sun, 1 Oct 2017 08:17:05 +0200 (CEST) Received: (qmail 87425 invoked by uid 500); 1 Oct 2017 06:17: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 87414 invoked by uid 99); 1 Oct 2017 06:17: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; Sun, 01 Oct 2017 06:17: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 4217D1A125E for ; Sun, 1 Oct 2017 06:17: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-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id mARjsplkKRar for ; Sun, 1 Oct 2017 06:17: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 D40835FDE7 for ; Sun, 1 Oct 2017 06:17: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 06CDBE00A7 for ; Sun, 1 Oct 2017 06:17: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 B134D242AF for ; Sun, 1 Oct 2017 06:17:00 +0000 (UTC) Date: Sun, 1 Oct 2017 06:17:00 +0000 (UTC) From: "James Taylor (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (PHOENIX-4219) Index gets out of sync on HBase 1.x MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 01 Oct 2017 06:17:06 -0000 [ https://issues.apache.org/jira/browse/PHOENIX-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187263#comment-16187263 ] James Taylor edited comment on PHOENIX-4219 at 10/1/17 6:16 AM: ---------------------------------------------------------------- I believe I've found the issue. Our RegionScanner implementation BaseScannerRegionObserver.RegionScannerHolder.nextRaw() is returning partial results which confuses Phoenix. Need to think about the best way of turning this off. How wide are the rows in general for your test, @Vincent Poon? [~sergey.soldatov] - this seems like another incarnation of PHOENIX-3112. We need to disable this "feature" (and add a unit test for it). It completely breaks Phoenix when it happens. was (Author: jamestaylor): I believe I've found the issue. Our RegionScanner implementation BaseScannerRegionObserver.RegionScannerHolder.nextRaw() is returning partial results which confuses Phoenix. Need to think about the best way of turning this off. > Index gets out of sync on HBase 1.x > ----------------------------------- > > Key: PHOENIX-4219 > URL: https://issues.apache.org/jira/browse/PHOENIX-4219 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.12.0 > Reporter: Vincent Poon > Priority: Blocker > Attachments: PHOENIX-4219_test.patch, PHOENIX-4219_test_v2.patch > > > When writing batches in parallel with multiple background threads, it seems the index sometimes gets out of sync. This only happens on the master and 4.x-HBase-1.2. > The tests pass for 4.x-HBase-0.98 > See the attached test, which writes with 2 background threads with batch size of 100. -- This message was sent by Atlassian JIRA (v6.4.14#64029)