Hi there, When sizing your data, don't forget to read thisŠ
http://hbase.apache.org/book.html#schema.creation and http://hbase.apache.org/book.html#regions.arch "9.7.5.4. KeyValue" You need to understand how Hbase stores data internally on initial design to avoid problems down the line. Keep the keys as small as reasonable, likewise CF name, and column names. On 12/17/12 6:07 AM, "Nicolas Liochon" <nkey...@gmail.com> wrote: >I think it's safer to use a newer version (0.94): there are a lot of >things >around performances & volumes in the 0.92 & 0.94. As well, there are much >more bug fixes releases on the 0.94. > >For the number of region, there is no maximum written in stone. Having too >many regions will essentially impact the performances. As I said, having >60TB of data per machine is not standard today (points are: that's a lot >of >disk a single machine; what's the impact if you lose a node; what will be >the network load, ...). I suppose all this is documented in the usual >books >on HBase. > > >On Mon, Dec 17, 2012 at 11:26 AM, tgh <guanhua.t...@ia.ac.cn> wrote: > >> number of region for ONE server?
