Hi. One additional issue with column families: number of memstores. Each family on insert utilizies one memstory. If you'll write in several memstores at onces you get more memstores and more memory will be used by you region server. Especially with random inserts you can easy get gc timeouts or OOME.
2010/10/10 <[email protected]>: > Hi folks, > I have a question about the scheme design for Hbase. In general, should I > prefer to have more column families with less column family qualifiers or > should I prefer to have less column families with more column family > qualifiers? > > For example, I could have one column family with four qualifiers inside or I > could have four column families with one qualifier in each of them, which > one should I use? > > I understand that each column family is going to be stored in a store. So, > my understanding is that: performance wise, it would be reasonable to choose > 1 column family with 4 qualifiers in the example above; considering the > sparse storage space, it would be reasonable to choose 4 column families > with 1 qualifier in the example above. Is this correct? > > Many thanks. > > > William >
