Re:Re: Re: What is the purpose of these system tables(CATALOG, STATS, and SEQUENCE)?

2015-01-13 Thread David chen
Hi James, Following your approach, i reduce the region number of SYSTEM.SEQUENCE to 2. But a new problem was subsequently appeared. When executing select * from SYSTEM.SEQUENCE;, encountered the following error: Error: ERROR 604 (42P00): Syntax error. Mismatched input. Expecting NAME, got

Re:Re: Re: What is the purpose of these system tables(CATALOG, STATS, and SEQUENCE)?

2014-12-23 Thread chenwenhui
Hi James, Thanks for your help. The SYSTEM.SEQUENCE has contained 256 regions in the production cluster, if modify phoenix.sequence.saltBuckets to the less value, will the region number reduce after restarting hbase service? Sorry for my chatter, after all restarting the productive cluster is

Re: Re: What is the purpose of these system tables(CATALOG, STATS, and SEQUENCE)?

2014-12-23 Thread James Taylor
Hi David, bq. Too many regions can easily burden the hbase cluster heavily, even if empty region Is that true, HBase-committers? You'll need to delete the SYSTEM.SEQUENCE, make sure to set the phoenix.sequence.saltBuckets property, and bounce your cluster. Then the next time you try to establish

Re: Re: What is the purpose of these system tables(CATALOG, STATS, and SEQUENCE)?

2014-12-21 Thread James Taylor
Like I said before, no it's not ok to drop system tables. If for some reason you don't want the sequence table presplit 256 ways, you can set the phoenix.sequence.saltBuckets to specify how many pre-split regions you'd like it to have (including setting it to 0). On Sun, Dec 21, 2014 at 5:38