Hi, James
Yes, we are running 4.2.2
Neither of these two configs are overridden. Do these configuration only affects stats collection?
I had not searched for the regionserver log for refering if any major compaction is running.

Just curious about the query performance. Cause we are good to count on that perviously.



From: James Taylor
Date: 2015-01-15 17:10
To: user
Subject: Re: rpc timeout when count on large table
You're on 4.2.2, Sun? Have you overridden either of
phoenix.stats.guidepost.width or phoenix.stats.guidepost.per.region?
These control the size of each parallel scan. I assume you've run a
major compaction on the table at some point?
On Wed, Jan 14, 2015 at 7:06 PM, sunfl@certusnet.com.cn
<sunfl@certusnet.com.cn> wrote:
> Hi, all
> When counting on large table, we got the following exception
>   org.apache.hadoop.hbase.ipc.RpcClient$CallTimeoutException: Call id=,
> waitTime=69714 rpcTimetout=60000
> How would that be resolved? Table size goes to 17.3G with issuing hdfs dfs
> -du. Table with 90+ columns
> and only one column family F. Compression codec is snappy.
> Thanks,
> Sun.
> ________________________________
> ________________________________
> CertusNet