[ https://issues.apache.org/jira/browse/HBASE-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212499#comment-13212499 ]
Jai Kumar Singh commented on HBASE-5166: ---------------------------------------- @Zhihong Yu, 1) Apache License was earlier there but I removed that become stack suggested so. Anyway, I'd put it back. 2) I've added Thread.sleep(1000). I am not sure whether we want to limit the wait duration, wouldn't that depend on kind of job we are running ? 3) I've modified the test case of TableMapper in src/test/java/org/apache/hadoop/hbase/mapreduce/TestTableMapReduce.java Firstly, I was going to make a new testcase file for MultithreadedTableMapper but it does not make sense in doing so, because that would be too much code repetition. So, I added a numOfThreads argument in TestTableMapReduce's runTestOnTable function and called the function twice. Check patch for more details. > MultiThreaded Table Mapper analogous to MultiThreaded Mapper in hadoop > ---------------------------------------------------------------------- > > Key: HBASE-5166 > URL: https://issues.apache.org/jira/browse/HBASE-5166 > Project: HBase > Issue Type: Improvement > Reporter: Jai Kumar Singh > Priority: Minor > Labels: multithreaded, tablemapper > Attachments: 0001-Added-MultithreadedTableMapper-HBASE-5166.patch, > 0003-Added-MultithreadedTableMapper-HBASE-5166.patch, > 0005-HBASE-5166-Added-MultithreadedTableMapper.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > There is no MultiThreadedTableMapper in hbase currently just like we have a > MultiThreadedMapper in Hadoop for IO Bound Jobs. > UseCase, webcrawler: take input (urls) from a hbase table and put the content > (urls, content) back into hbase. > Running these kind of hbase mapreduce job with normal table mapper is quite > slow as we are not utilizing CPU fully (N/W IO Bound). > Moreover, I want to know whether It would be a good/bad idea to use HBase for > these kind of usecases ?. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira