hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: HBASE-3904
Date Sat, 09 Jul 2011 20:45:14 GMT
I resolved HBASE-3904 because there was no solution that everyone agreed on.

On Sat, Jul 9, 2011 at 12:48 PM, M. C. Srivas <mcsrivas@gmail.com> wrote:

> Its not clear from hbase-3904 what the issues are. If there's some code
> relying on isTableAvailable, that code is inherently broken.
>
> 1. isTableAvailable() is never reliable, because
>     (a) if it returns true, the table can disappear immediately after the
> call finishes, or
>     (b) the table can appear immediately after the call returns false
>
> 2. In the normal situation, where some RS's could be down (while most are
> up), it would be correct for  isTableAvailable() to return true. But the
> caller cannot rely on it unless they do a get() on the row they are
> interested in.
>
> Ted, could you explain your concern?
>
> On Fri, Jul 8, 2011 at 1:22 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>
> > Hi,
> > I want to get your opinion on what should be done for HBASE-3904 beyond
> > making createTable() synchronous.
> >
> > Thanks
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message