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 D8796F52 for ; Mon, 20 Aug 2012 17:41:38 +0000 (UTC) Received: (qmail 98863 invoked by uid 500); 20 Aug 2012 17:41:38 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 98793 invoked by uid 500); 20 Aug 2012 17:41:38 -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 98784 invoked by uid 99); 20 Aug 2012 17:41:38 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2012 17:41:38 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 46CD52C04AC for ; Mon, 20 Aug 2012 17:41:38 +0000 (UTC) Date: Tue, 21 Aug 2012 04:41:37 +1100 (NCT) From: "Zhihong Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: <909006223.30713.1345484498291.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HBASE-6617) ReplicationSourceManager should be able to track multiple WAL paths MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Zhihong Ted Yu created HBASE-6617: ------------------------------------- Summary: ReplicationSourceManager should be able to track multiple WAL paths Key: HBASE-6617 URL: https://issues.apache.org/jira/browse/HBASE-6617 Project: HBase Issue Type: Sub-task Reporter: Zhihong Ted Yu Currently ReplicationSourceManager uses logRolled() to receive notification about new HLog and remembers it in latestPath. When region server has multiple WAL support, we need to keep track of multiple Path's in ReplicationSourceManager -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira