You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nate Putnam (JIRA)" <ji...@apache.org> on 2013/01/15 20:34:12 UTC

[jira] [Commented] (HBASE-5640) bulk load runs slowly than before

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

Nate Putnam commented on HBASE-5640:
------------------------------------

We had an issue with this a while back. The impact was that things would timeout because of the intermediate copy. 

Sat Jun 30 13:50:25 EDT 2012, org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles$3@2afd97ea, java.net.SocketTimeoutException: Call to proc22.prod.urbanairship.com/10.128.12.38:7040 failed on socket timeout exception: java.net.SocketTimeoutException: 60000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/10.128.12.40:45456 remote=proc22.prod.urbanairship.com/10.128.12.38:7040]

at org.apache.hadoop.hbase.client.ServerCallable.withRetries(ServerCallable.java:183)
at org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.tryAtomicRegionLoad(LoadIncrementalHFiles.java:491)

Applying this patch fixed the issue and sped things up significantly. 
                
> bulk load runs slowly than before
> ---------------------------------
>
>                 Key: HBASE-5640
>                 URL: https://issues.apache.org/jira/browse/HBASE-5640
>             Project: HBase
>          Issue Type: Bug
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>            Priority: Minor
>              Labels: bulkloader
>         Attachments: bulkLoadFs1.txt, bulkLoadFs2.txt
>
>
> I am loading data from an external system into hbase. There are many prints of the form. This is possibly a regression caused by a recent patch.
> ....on different filesystem than destination store - moving to this filesystem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira