question about composite rowKey and performance difference between getScanner() and get(Get[])

2014-12-04 Thread Marc Sturm
Hi, I have a many to many relationship that I am trying to model in hbase, and I want to be sure I am not missing anything so please let me know or point to the right documentation. Let's say I have an A to B many to many relationship, the query parameter takes A unique id and returns all the

use the importtsv tools How i improv the reduce the concurent progress?

2014-12-04 Thread jackie
dear all! I used the importtsv tools trnaslate the txt file to the Hfile (hadoop 2.2.0 ,hbase 0.96.2).Map procedure have many the concurent progress,but reduce procedure has always 1 progress.How do i improv the reduce the concurent progress? Thank u very much! Best regards!

Re: client timeout

2014-12-04 Thread lars hofhansl
Bad disk or network? Anything in the logs (HBase, HDFS, and System logs)? HBase 0.94, still?The easiest way to just kill the region servers, the others will pick up the regions. -- Lars From: Ted Tuttle t...@mentacapital.com To: user@hbase.apache.org user@hbase.apache.org Cc: Development

Re: Using HBase Thrift API to move a number of rows

2014-12-04 Thread Nick Dimiduk
I believe so, yes. Your client would take note of the last row key returned and use that to decide on the new start row key. On Sun, Nov 30, 2014 at 10:58 AM, Néstor Boscán nesto...@gmail.com wrote: Hi Nick So what do I use to seek from row 10? The start row? Regards, Néstor On Fri, Nov

Re: Help,use the importtsv tools

2014-12-04 Thread Shahab Yunus
You need to pre-split the table into regions as in this tool the number of reducers are driven by the number of regions in the target table. Read about it here: http://hbase.apache.org/book/perf.writing.html http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/ Regards, Shahab

RE: client timeout

2014-12-04 Thread Ted Tuttle
Sort of :( The server-side errors below started showing up on node5. We took node5 down and then they started on node7. Then we brought back node5 and were still seeing the errors on node7. So we bounced node7. The errors went back to node5. We bounced node5 a second time and that