For #2, partial row would be returned. Please take a look at the following method in RSRpcServices around line 2393 :
public ScanResponse scan(final RpcController controller, final ScanRequest request) Cheers On Wed, May 13, 2015 at 12:59 AM, David chen <[email protected]> wrote: > Thanks for you reply. > Yes, it indeed appeared in the RegionServer command as follows: > jps -v|grep "Region" > HRegionServer -Dproc_regionserver -XX:OnOutOfMemoryError=kill -9 %p > -Xmx1000m -Djava.net.preferIPv4Stack=true -Xms16106127360 -Xmx16106127360 > -XX:+UseG1GC -XX:MaxGCPauseMillis=6000 > -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh > > > After read HBASE-11544, i have some doubts: > 1. Assume scan has set caching to 1 and batch to 1, for a row with 2 > cells, the first RPC should only return a cell of the row, it is also the > partial of a row. Unless the cell is too large size, otherwise, will not > need HBASE-11544. right? > 2. Assume scan has set caching to 1 and maxResultSize to 1, for a row > which per cell size is more than 1, will the first RPC return the whole or > partial row? I think the whole row, right? > > > > > > > > > > > At 2015-05-13 11:04:04, "Ted Yu" <[email protected]> wrote: > >Does the following appear in the command which launched region server ? > >-XX:OnOutOfMemoryError="kill -9 %p" > > > >There could be multiple reasons for region server process to encounter > OOME. > >Please take a look at HBASE-11544 which fixes a common cause. The fix is > in > >the upcoming 1.1.0 release. > > > >Cheers > > > >On Tue, May 12, 2015 at 7:41 PM, David chen <[email protected]> wrote: > > > >> A RegionServer was killed because OutOfMemory(OOM), although the > process > >> killed can be seen in the Linux message log, but i still have two > following > >> problems: > >> 1. How to inspect the root reason to cause OOM? > >> 2 When RegionServer encounters OOM, why can't it free some memories > >> occupied? if so, whether or not killer will not need. > >> Any ideas can be appreciated! >
