Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 45B051839F for ; Thu, 14 May 2015 02:06:00 +0000 (UTC) Received: (qmail 74515 invoked by uid 500); 14 May 2015 02:06:00 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 74457 invoked by uid 500); 14 May 2015 02:06:00 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 74445 invoked by uid 99); 14 May 2015 02:06:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2015 02:06:00 +0000 Date: Thu, 14 May 2015 02:06:00 +0000 (UTC) From: "Matteo Bertozzi (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-13685) Procedure v2 - Add maxProcId to the wal header MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Matteo Bertozzi created HBASE-13685: --------------------------------------- Summary: Procedure v2 - Add maxProcId to the wal header Key: HBASE-13685 URL: https://issues.apache.org/jira/browse/HBASE-13685 Project: HBase Issue Type: Sub-task Components: proc-v2 Affects Versions: 1.1.0 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Priority: Blocker Fix For: 1.1.0 Attachments: HBASE-13685-v0.patch while working on HBASE-13476 I found that having the max-proc-id in the wal header, allows some nice optimizations. [~ndimiduk] since 1.1 is not released yet, can we get this in so we can avoid all extra handling? -- This message was sent by Atlassian JIRA (v6.3.4#6332)