[ 
https://issues.apache.org/jira/browse/HBASE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709581#action_12709581
 ] 

Jim Kellerman commented on HBASE-1177:
--------------------------------------

On our cluster:

{code}
Same machine as server hosting table

Read 1 row with 7 columns 100 times in 206ms
Read 1 row with 8 columns 100 times in 4018ms
Read 1 row with 1000 columns 100 times in 13392ms

Different machine as server hosting table

Read 1 row with 7 columns 100 times in 152ms
Read 1 row with 8 columns 100 times in 168ms
Read 1 row with 1000 columns 100 times in 9386ms
{code}

> Delay when client is located on the same node as the regionserver
> -----------------------------------------------------------------
>
>                 Key: HBASE-1177
>                 URL: https://issues.apache.org/jira/browse/HBASE-1177
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.19.0
>         Environment: Linux 2.6.25 x86_64
>            Reporter: Jonathan Gray
>            Assignee: Jim Kellerman
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: ReadDelayTest.java
>
>
> During testing of HBASE-80, we uncovered a strange 40ms delay for random 
> reads.  We ran a series of tests and found that it only happens when the 
> client is on the same node as the RS and for a certain range of payloads (not 
> specifically related to number of columns or size of them, only total 
> payload).  It appears to be precisely 40ms every time.
> Unsure if this is particular to our architecture, but it does happen on all 
> nodes we've tried.  Issue completely goes away with very large payloads or 
> moving the client.
> Will post a test program tomorrow if anyone can test on a different 
> architecture.
> Making a blocker for 0.20.  Since this happens when you have an MR task 
> running local to the RS, and this is what we try to do, might also consider 
> making this a blocker for 0.19.1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to