From the code, hbase.hregion.majorcompaction=0 is not to turn off major
compaction...I did a search and find a good(but a little long) post on this
topic and performance tuning on write heavy workload:
http://apache-hbase.679495.n3.nabble.com/Major-Compaction-Concerns-td3642142.html
Personally
For #1, what's the expected size of data you want to store ?
For #2, the new data inserted under column:value with a newer timestamp
would be stored in a different HFile. Old and new data would be
consolidated after major compaction.
Cheers
On Mon, Nov 10, 2014 at 6:21 AM, Bill Q
Hi Ted,
Thanks a lot for the reply.
For #1, the size for the value only will be around 20 bytes for each cell.
And there will be hundreds of thousands of time stamp per cell. But not
millions. Any suggestion?
Many thanks.
Cao
On Monday, November 10, 2014, Ted Yu yuzhih...@gmail.com wrote:
Hi Ted,
Thanks a lot.
When would it break? Would you please give some details of why the size
would be a decision factor?
I will have probably 10 cells that have daily updates. And the rest cells
in the column family will only have a handful of versions. So, the cells in
the same column family
Hi:
command:hbase hbck -fixAssignments Error,for help!!
Exception in thread main java.io.IOException: Region {NAME =
'n2_outer_role_exp_inc_reason,2014-10-25#4#0014#000all#all#001#all#all#5173
5361 1 4 0 0 9 6218 6597,1415326476019.1ff44b508ad964be8b0a1a282f0b67c2.',
STARTKEY =
Any help here?
On Fri, Nov 7, 2014 at 5:18 PM, Flavio Pompermaier pomperma...@okkam.it
wrote:
Hi to all,
in the TableInputFormatBase there's a method that computes the splits that
depends on the region start/end key. I'd like to further split each split
so that to be able to assign work in
Have you checked master log searching for this region to see what happened ?
What release of hbase are you using ?
bq. #5173 5361 1 4 0 0 9 6218 6597
There were spaces in the above string. Typo ?
Cheers
On Sun, Nov 9, 2014 at 10:22 PM, Coma Guy tang...@everbuys.com wrote:
Hi:
command:hbase
I’m running a map/reduce job against a table that is performing a large number
of writes (probably updating every row).
The job is failing with the exception below. This is a solid failure; it dies
at the same point in the application,
and at the same row in the table. So I doubt it’s a conflict
There could be more than one reason where RegionTooBusyException is thrown.
Below are two (from HRegion):
* We throw RegionTooBusyException if above memstore limit
* and expect client to retry using some kind of backoff
*/
private void checkResources()
* Try to acquire a lock.
How many tasks may write to this row concurrently ?
only 1 mapper should be writing to this row. Is there a way to check which
locks are being held?
Which 0.98 release are you using ?
0.98.0.2.1.2.1-471-hadoop2
Thanks
Brian
On Nov 10, 2014, at 2:21 PM, Ted Yu yuzhih...@gmail.com wrote:
When I call the function 'getRow', it returns array.
But I couldn't find any documents about order of data sequence.
For instance,
Presume that a column family is 'c' and qualifiers start from 'c:000' to
'c:100'.
And when I call the function like below
$rowarr = getRow($table, $rowkey);
Was the region containing this row hot around the time of failure ?
Can you check region server log (along with monitoring tool) what memstore
pressure was ?
Thanks
On Nov 10, 2014, at 11:34 AM, Brian Jeltema brian.jelt...@digitalenvoy.net
wrote:
How many tasks may write to this row
Hi all,
The next HBase user group meeting is on November the 20th. We need a
few more presenters still!
Please send me your proposals - summary and outline of your talk!
Thanks!
-ryan
Was the region containing this row hot around the time of failure ?
How do I measure that?
Can you check region server log (along with monitoring tool) what memstore
pressure was ?
I didn't see anything in the region server logs to indicate a problem. And
given the
reproducibility of
Hi Ted:
thanks for your feedback. I tried to clone for_hbase_0.98 branch by: git
clone https://github.com/XiaoMi/themis/tree/for_hbase_0.98;, it returns:
error: The requested URL returned error: 403 while accessing
https://github.com/XiaoMi/themis/tree/for_hbase_0.98/info/refs;.
I think we
Thanks Jianwei for the suggestion.
I checked out for_hbase_0.98 but got the following error when building:
[ERROR] Failed to execute goal on project themis-protocol: Could not
resolve dependencies for project
com.xiaomi.infra:themis-protocol:jar:1.0-SNAPSHOT: Could not find artifact
bq. do we have hadoop2 version for hbase 0.94 in central maven repository?
Not that I know of.
w.r.t. dependency on hbase-annotations module, maybe you can introduce a
new profile that includes this dependency.
Cheers
On Mon, Nov 10, 2014 at 7:18 PM, 崔建伟 cuijian...@xiaomi.com wrote:
Hi Ted:
Hi Ted:
Thanks for your advice. Yes, it is more reasonable to add common properties in
parent pom:). I update themis to set hbase version/hadoop version in parent
pom, and set hbase version to 0.98.5-hadoop2 for for_hbase_0.98 branch. The
unit tests are passed under these modifications.
18 matches
Mail list logo