Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of whshub@gmail.com designates
 209.85.212.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1327709013.41476.YahooMailNeo@web121702.mail.ne1.yahoo.com>
References: 
 <CAO83RbXzdBqOdPbak2BR0ytAwu1WOkqfQiUzUeKgSCTZsBpg5A@mail.gmail.com>
	<1327709013.41476.YahooMailNeo@web121702.mail.ne1.yahoo.com>
Date: Fri, 27 Jan 2012 16:17:37 -0800
Message-ID: 
 <CAO83RbWSM_KrcmChRHVqhAZ69vam=+ZD3uXdfoSS7svOE-Wv2w@mail.gmail.com>
Subject: Re: Thoughts on HBASE-2357? (read-only slaves)
From: Jacques <whshub@gmail.com>
To: dev@hbase.apache.org, lars hofhansl <lhofhansl@yahoo.com>
Content-Type: multipart/alternative; boundary=f46d043c08d866a3a204b78b8a75

--f46d043c08d866a3a204b78b8a75
Content-Type: text/plain; charset=ISO-8859-1

Thanks for the pointer to HBASE-2196.

My use case is more to minimize downtime (better to serve stale data than
to wait for region transition).  I was just curious if anyone had started
putting code to disk on the HBASE-2357.

Thanks,
Jacques

On Fri, Jan 27, 2012 at 4:03 PM, lars hofhansl <lhofhansl@yahoo.com> wrote:

> HBASE-2196 enables replication to multiple slaves.
> Those slaves need to be in different clusters, so it is not the same.
> Depends on your use case.
>
> -- Lars
>
>
>
> ----- Original Message -----
> From: Jacques <whshub@gmail.com>
> To: dev@hbase.apache.org
> Cc:
> Sent: Friday, January 27, 2012 2:00 PM
> Subject: Thoughts on HBASE-2357? (read-only slaves)
>
> I was wondering whether anyone is working on the read-only slave feature?
> I see that previously Andrew had hoped to implement this as a coprocessor.
> Any additional thoughts beyond what is in the bug comments?
>
> https://issues.apache.org/jira/browse/HBASE-2357
>
> Thanks
> Jacques
>
>

--f46d043c08d866a3a204b78b8a75--