For #1, it is the limit on a single keyvalue, not row, not key. For #2, please see the following:
http://hbase.apache.org/book.html#store.memstore http://hbase.apache.org/book.html#regionserver_splitting_implementation Cheers On Mon, Aug 17, 2015 at 7:36 AM, Shushant Arora <[email protected]> wrote: > 1.Is hbase.client.keyvalue.maxsize is max size of row or key only ? Is > there any limit on key size only ? > 2.Access pattern is mostly on key based only- Is memstores and regions on a > regionserver are per table basis? Is it if I have multiple tables it will > have multiple memstores instead of few if it would have been one large > table ? > > > On Mon, Aug 17, 2015 at 7:29 PM, Ted Yu <[email protected]> wrote: > > > For #1, take a look at the following in hbase-default.xml : > > > > <name>hbase.client.keyvalue.maxsize</name> > > <value>10485760</value> > > > > For #2, it would be easier to answer if you can outline access patterns > in > > your app. > > > > For #3, adjustment according to current region boundaries is done client > > side. Take a look at the javadoc for LoadQueueItem > > in LoadIncrementalHFiles.java > > > > Cheers > > > > On Mon, Aug 17, 2015 at 6:45 AM, Shushant Arora < > [email protected] > > > > > wrote: > > > > > 1.Is there any max limit on key size of hbase table. > > > 2.Is multiple small tables vs one large table which one is preferred. > > > 3.for bulk load -when LoadIncremantalHfile is run it again > recalculates > > > the region splits based on region boundary - is this division happens > on > > > client side or server side again at region server or hbase master and > > then > > > it assigns the splits which cross target region boundary to desired > > > regionserver. > > > > > >
