Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08B56BF2F for ; Mon, 16 Jan 2012 07:27:24 +0000 (UTC) Received: (qmail 12025 invoked by uid 500); 16 Jan 2012 07:27:23 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 11766 invoked by uid 500); 16 Jan 2012 07:27:12 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 11747 invoked by uid 99); 16 Jan 2012 07:27:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2012 07:27:08 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.138.91.23] (HELO nm8-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.23) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 16 Jan 2012 07:26:57 +0000 Received: from [98.138.90.55] by nm8.bullet.mail.ne1.yahoo.com with NNFMP; 16 Jan 2012 07:26:35 -0000 Received: from [98.138.87.4] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 16 Jan 2012 07:25:35 -0000 Received: from [127.0.0.1] by omp1004.mail.ne1.yahoo.com with NNFMP; 16 Jan 2012 07:25:35 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 709509.96944.bm@omp1004.mail.ne1.yahoo.com Received: (qmail 35828 invoked by uid 60001); 16 Jan 2012 07:25:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1326698735; bh=sKr/6ym+EMlDLWHaLZKK18eD9+DerGKCoJ6bf61EEg0=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Ql9pLmw41cGoXW+14svm5wUrqi+TcTfd0MVhEvihTImVrrnWaLm/PzyAkro+IEjoIcojnPE9eLqDSWeaGN13/AHfIXJsWOYTU2nE3J58dWvmaXjT/xMATLPU2REXNGzF0m0Z6BtFi2pAs7XgLhtl5wnhm/X2KPqniq54rPx3mJQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=3MGR5qiHEPZjIk6G1mm0IfDuZQU7C4BIljEfcEXUdTnJ/3WktveTJ5BOzXX9YvK9uZS1Q/cQKPPMz4a2N3MkRxqD/boqdZSWb1IzpPdh+e53L9kq7VdpKIZauxXI4KvkgD+NneOmFmEQ2XEydsdXGXHXPn8p0v+tsJfSKjicttA=; X-YMail-OSG: vKQqF48VM1nyqRWyo9C.H74x_yIckJ9vbr7LrgSQuDFgpbv aCN0Cx4tkLY98x8EEaU0DEG8LrPwOKFzAcTQZbQZYChFe6HBT2LAWh.I2DDX vVPS072Xwc0kd.qiXvGwcVd3MX0v2iMerPX2cmjskofHdfysH_kUT2xTuvWk snlBX9QjywufghxuO5xXE13Q4rQ.HpWFBT9on3A5A8CoonGMoa0ZZIwmXN1z Ync.4Mzmq.C1oKoU2W0aRveJt9MC7QTMIANfpud8paILUhMKm8QlnywOTIRH SEBI_.p6f0e.GJ_aIQZ5p9EK_3X48um5B7UetlTeSo8zoHK9TFDgQwLmVupy sH3wAHRo4ftXUhbzW_oHhxRpfDhvLqkMmw05rFeQlfbqAenk7jAmEmzl99a2 JUR459AGJaV5Srhdk2ykTiZcTk8Ped6K1Rn.jCrl3OCF0VmyAqOQl5pYw7gd 2H1PWjQ-- Received: from [69.181.180.38] by web121701.mail.ne1.yahoo.com via HTTP; Sun, 15 Jan 2012 23:25:35 PST X-Mailer: YahooMailWebService/0.8.115.331698 References: <1326697270.46783.YahooMailNeo@web121703.mail.ne1.yahoo.com> Message-ID: <1326698735.27778.YahooMailNeo@web121701.mail.ne1.yahoo.com> Date: Sun, 15 Jan 2012 23:25:35 -0800 (PST) From: lars hofhansl Reply-To: lars hofhansl Subject: Re: HTable.flushCommits and ordering To: "dev@hbase.apache.org" In-Reply-To: <1326697270.46783.YahooMailNeo@web121703.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org It's late... Never mind... Everything is timestamped... So order does not matter. ----- Original Message ----- From: lars hofhansl To: hbase-dev Cc: Sent: Sunday, January 15, 2012 11:01 PM Subject: HTable.flushCommits and ordering Here's another strange client behavior: When autoFlush is set to false on HTable (or HTable.batch is used), this triggers a Multi action at the RegionServer. However, the RegionServer collects all Puts and executes those after all other action (presumably to make use of batching for Puts). If the batch contains Deletes that is not correct, since the order of Deletes w.r.t. Puts is significant. I am adding the option to force execution in the provided order (default false), which would retain the order of Puts/Deletes/etc, but comes with a performance penalty at the server (it is still a single roundtrip, though, which is good). I'll attach a patch for this (as part of a bigger change) to HBASE-5203 soon. Please provide your comments. Thanks. -- Lars