hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: ResultScanner performance
Date Wed, 27 Aug 2014 03:35:42 GMT
Keeping many ResultScanners open at the same time is not good for
performance.

Please see:
http://hbase.apache.org/book.html#perf.hbase.client.scannerclose

After fetching results from ResultScanner, you should close it ASAP.

Cheers


On Tue, Aug 26, 2014 at 8:18 PM, Dai, Kevin <yundai@ebay.com> wrote:

> Hi, Ted
>
> We have a cluster of 48 machines and at least 100T data(which is still
> increasing).
> The problem is that we have a lot of row keys (about tens of thousands )
> to query in the meantime and we don't fetch all the data at once, instead
> we fetch them when needed,
> so we may hold tens of thousands ResultScanner in the meantime.
> I want to know whether it will hurt the performance and network resources
> and if so, is there any way to solve it?
>
> Best regards,
> Kevin.
> -----Original Message-----
> From: Ted Yu [mailto:yuzhihong@gmail.com]
> Sent: 2014年8月26日 16:49
> To: user@hbase.apache.org
> Cc: user@hbase.apache.org; Huang, Jianshi
> Subject: Re: ResultScanner performance
>
> Can you give a bit more detail ?
> What size is the cluster / dataset ?
> What problem are you solving ?
> Would using coprocessor help reduce the usage of ResultScanner ?
>
> Cheers
>
> On Aug 26, 2014, at 12:13 AM, "Dai, Kevin" <yundai@ebay.com> wrote:
>
> > Hi, everyone
> >
> > My application will hold tens of thousands of ResultScanner to get Data.
> Will it hurt the performance and network resources?
> > If so, is there any way to solve it?
> > Thanks,
> > Kevin.
>

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