Hi..
Based on this little information Check you rowkey design along with
what splitting policy you are using.
Thanks
Manjeet
On Mon, Jan 9, 2017 at 3:20 PM, Rajeshkumar J
wrote:
> we have 7000 regions in which we only have data in 20 regions. Whether this
> may be the reason for this?
>
>
we have 7000 regions in which we only have data in 20 regions. Whether this
may be the reason for this?
On Thu, Jan 5, 2017 at 10:58 PM, Stack wrote:
> On Thu, Jan 5, 2017 at 6:09 AM, Rajeshkumar J >
> wrote:
>
> > Adding this
> > Here Clauster have three machines each have 125 GB as RAM in whi
On Thu, Jan 5, 2017 at 6:09 AM, Rajeshkumar J
wrote:
> Adding this
> Here Clauster have three machines each have 125 GB as RAM in which 70 GB is
> free, One Machine acts as HMaster and also Region Server. Another machine
> acts as Secondary Hmaster and also Region Server. Third Machine is a
> ded
Adding this
Here Clauster have three machines each have 125 GB as RAM in which 70 GB is
free, One Machine acts as HMaster and also Region Server. Another machine
acts as Secondary Hmaster and also Region Server. Third Machine is a
dedicated Hregion Server. We have about 7000 Regions.
Maybe is this
(Thanks for jumping in Billy)
Smaller Scans? (This is good on Scans in 1.1.+ which you seem to be on:
https://blogs.apache.org/hbase/entry/scan_improvements_in_hbase_1)
Otherwise look at other factors. Are the servers loaded? GC on
client/server or resources being taken up by adjacent processes;
Disclaimer: this is what I think I know and I'm not an HBase contributor...
Anytime we get scanner timeouts like that, we first expand the timeout
itself like you're doing to fix the short-term problem. But then we look at
our rowkey design and what we're doing. Timeouts like that are usually
symp
Hi Stack,
Yes it worked. I had a serious doubt regarding lease does not exist
exception. We have 30 tables which have 45 million records each. We are
scanning the table initially process is successful but after it gets failed
with lease does not exist exception. By changing hbase.rpc.timeout an
Yeah. Try it.
S
On Tue, Jan 3, 2017 at 9:18 PM, Rajeshkumar J
wrote:
> So I need to add property in log4j.properties as below
>
> log4j.logger.org.apache.hadoop.hbase.ipc.RpcServer = TRACE
>
> On Wed, Jan 4, 2017 at 10:23 AM, Stack wrote:
>
> > See http://hbase.apache.org/book.html#log4j
> >
>
So I need to add property in log4j.properties as below
log4j.logger.org.apache.hadoop.hbase.ipc.RpcServer = TRACE
On Wed, Jan 4, 2017 at 10:23 AM, Stack wrote:
> See http://hbase.apache.org/book.html#log4j
>
> Or to set it temporarily via UI, see
> http://hbase.apache.org/book.html#trouble.log.
See http://hbase.apache.org/book.html#log4j
Or to set it temporarily via UI, see
http://hbase.apache.org/book.html#trouble.log.levels
St.Ack
On Tue, Jan 3, 2017 at 6:58 PM, Rajeshkumar J
wrote:
> Do we have to include this property in hbase-site.xml?
>
> On Wed, Jan 4, 2017 at 2:12 AM, Stack
Do we have to include this property in hbase-site.xml?
On Wed, Jan 4, 2017 at 2:12 AM, Stack wrote:
> On Mon, Jan 2, 2017 at 10:32 PM, Rajeshkumar J <
> rajeshkumarit8...@gmail.com>
> wrote:
>
> > Do all rpc calls are logged in hbase region server log? Also I need to
> find
> > the time taken fo
On Mon, Jan 2, 2017 at 10:32 PM, Rajeshkumar J
wrote:
> Do all rpc calls are logged in hbase region server log? Also I need to find
> the time taken for each scan calls is this possible
>
> If you enable trace level logging for the rpcserver class,
org.apache.hadoop.hbase.ipc.RpcServer, then you
Do all rpc calls are logged in hbase region server log? Also I need to find
the time taken for each scan calls is this possible
Thanks
13 matches
Mail list logo
