Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CC72610FA5 for ; Tue, 25 Feb 2014 15:53:50 +0000 (UTC) Received: (qmail 29390 invoked by uid 500); 25 Feb 2014 15:53:49 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 29343 invoked by uid 500); 25 Feb 2014 15:53:49 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 29327 invoked by uid 99); 25 Feb 2014 15:53:49 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 15:53:48 +0000 Received: from localhost (HELO mail-la0-f48.google.com) (127.0.0.1) (smtp-auth username vines, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 15:53:47 +0000 Received: by mail-la0-f48.google.com with SMTP id gf5so4224101lab.7 for ; Tue, 25 Feb 2014 07:53:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=jtMBGySynaRotPTwF7g2T9Abdi3u/tFtaPTeJzt1ZDg=; b=k9SFmLcwq+Z3ZNbVM5BWi9w1WjsD6AKskWqX2Rt7o2JdIXcznV4BKhrpP92okt1cvH Vtng6eSNFkjRk+Iz7HMjN/rdRX/IwnPFSNfZMGXZMbiIwfgqnC9lf/Bbn8ZiXiSGn5Oq hZLasbUoYfvaAKLwxwJMawFf6w2pvF71xZpcs5v8CpBAOPZPXB0vnRd5TUORN4FtrXpU A4zEWmw4ieMctzZA0+rWPAbsQRLwIQqjSJ+/jKOg8De6HcHa3jbQA7bnwAjkmba80J0M QB6KDrkxXP57/OloD8tLV2iQUJnMMRvA6rI0lqTuwlqMqmNbdtsHduT2mNvbcjndMtxZ B9hw== X-Received: by 10.152.36.70 with SMTP id o6mr324949laj.7.1393343625914; Tue, 25 Feb 2014 07:53:45 -0800 (PST) MIME-Version: 1.0 Reply-To: vines@apache.org Received: by 10.114.93.3 with HTTP; Tue, 25 Feb 2014 07:53:05 -0800 (PST) In-Reply-To: References: From: John Vines Date: Tue, 25 Feb 2014 10:53:05 -0500 Message-ID: Subject: Re: HDFS caching w/ Accumulo? To: "user@accumulo.apache.org" Content-Type: multipart/alternative; boundary=089e0160b618df6d7404f33d1722 --089e0160b618df6d7404f33d1722 Content-Type: text/plain; charset=ISO-8859-1 I could see it being used for the metadata and root table files, at a minimum. Also useful for other reused information in HDFS- tableId for HdfsZooInstance, KeyEncryptionKey if that's being used. Maybe root/metadata WALogs as well. On Tue, Feb 25, 2014 at 10:49 AM, Donald Miner wrote: > HDFS caching is part of the new Hadoop 2.3 release. From what I > understand, it allows you to mark specific files to be held in memory for > faster reads. > > Has anyone thought about how Accumulo could leverage this? > --089e0160b618df6d7404f33d1722 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I could see it being used for the metadata and root table = files, at a minimum. Also useful for other reused information in HDFS- tabl= eId for HdfsZooInstance, KeyEncryptionKey if that's being used. Maybe r= oot/metadata WALogs as well.


On Tue, Feb 2= 5, 2014 at 10:49 AM, Donald Miner <dminer@clearedgeit.com> wrote:
HDFS caching is part o= f the new Hadoop 2.3 release. From what I understand, it allows you to mark= specific files to be held in memory for faster reads.

Has anyone thought about how Accumulo could leverage this?

--089e0160b618df6d7404f33d1722--