Home | About | Sematext search-lucene.com search-hadoop.com
clear query|facets|time Search criteria: prefix salt key hotspot.   Results from 1 to 10 from 38 (0.077s).
Did you mean:
SpellChecker(?): prefix sat key hotspot 
Loading phrases to help you
refine your search...
Re: Adding a new region server or splitting an old region in a Hash-partitioned HBase Data Store - HBase - [mail # user]
...://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-despite-writing-records-with-sequential-keys/  And some older discussions by experts on this topic: http://search-hadoop.com/?q=prefix+salt+key+hotspot...
   Author: Shahab Yunus, 2013-06-27, 15:11
Re: Rowkey hashing to avoid hotspotting - HBase - [mail # user]
... hot data (like in example above: with keys prefixed with model, the whole several regions containing data of same model may have data that is frequently accessed). In this case HBase...
...You might be right, when reading load concentrated on single/several RS they will not act as dead as when it is hotspotting during writing. I think I referred more to "uneven read load...
[+ show more]
   Author: Alex Baranau, 2012-07-17, 18:49
RES: Rowkey hashing to avoid hotspotting - HBase - [mail # user]
... r anymore. 2 - Salting, by prefixing your current rowkey with a pinch of hash. Notice  that the hash portion must be your rowkey prefix to ensure a kind of balanc ed distribution over...
...Hi Anand,  As usual, the answer is that 'it depends'  :)  I think that the main question here is: why are you afraid that this setup  would lead to region server hotspotting? Is because you...
[+ show more]
   Author: Cristofer Weber, 2012-07-16, 19:00
Re: HBase Region/Table Hotspotting - HBase - [mail # user]
... of the key (but then you loose the ability to do range scan across keys).  If you still need to scan rows according to their sort order you can "salt" (as some call it) the key by prefix...
...The most common cause for hotspotting is inserting rows with monotonically increasing row keys. In that case only the last region will get the writes and no amount of splitting will fix...
[+ show more]
   Author: lars hofhansl, 2013-02-11, 05:14
Timestamp as a key good practice? - HBase - [mail # user]
....  With this schema, I can find the files by ID very quickly and I can find the files which need to be updated pretty quickly too. But it's hotspotting one region.  1) Hotspotting. 2) Salting. 3) Key field...
... until the timestamp reach a certain value and move to the next region (hotspotting).  I have a table with a uniq key, a file path and a "last update" field. I can easily find back the file...
[+ show more]
   Author: Jean-Marc Spaggiari, 2012-06-13, 16:16
key design - HBase - [mail # user]
...Hello folks,  i am trying to come up with a nice key design for storing logs in the company. I am planning to index them  and store row key in the index for random reads.  I need to balance...
... the writes equally between the R.S. and i could not understand how opentsdb does that with prefixing the metric id. (i related metric id with the log type) In my log storage case a log line just has...
[+ show more]
   Author: mete, 2012-05-21, 14:56
Consider individual RSs performance when writing records with random keys? - HBase - [mail # user]
.../timeseries data. If simplified, the idea is to add random prefix to the row key so that writes end up on different region servers (avoiding single RS hotspot).  2. When writing data to HBase with salted...
...Hi,  1. Not sure if you've seen HBaseWD (https://github.com/sematext/HBaseWD) project. It implements the "salt keys with prefix" approach when writing monotonically increasing row key...
[+ show more]
   Author: Alex Baranau, 2012-05-17, 14:23
Re: Is there a problem with having 4000 tables in a cluster? - HBase - [mail # user]
...So you should salt the keys in the reduce phase but u donot salt the keys in HBase. That basically means that reducers do not see the keys in sorted order but they do see all the values...
... for a specific key together.  So the Hash essentially is a trick that stays within the mapreduce does not make it into HBase. This prevents you from hotspotting a region and since the Hash is not being...
[+ show more]
   Author: Varun Sharma, 2013-09-24, 23:22
RE: Row Keys - HBase - [mail # user]
... into the Mozilla Socorro project (http://code.google.com/p/socorro/) for how to "salt" the keys to get better load balancing across sequential keys. The principle is to add a salt, in this case a number...
... reflecting the number of servers available (some multiple of that to allow for growth) and then prefix the sequential key with it so that writes are spread across all servers. For example "-". When...
[+ show more]
   Author: Peter Haidinyak, 2011-01-31, 16:45
Re: Hash keys - HBase - [mail # user]
....  I was first confused reading "row 1...1000 -> prefix h1_". To really make the distribution random, I would have seen prefix/salt  attributed randomly for a key leading to for example a h1...
..., you may need to do some range  queries, and adding a salt can be an answer to combine best-of-world.  I understand the "salt" approach as recreating on the client side  "artifical" key spaces...
[+ show more]
   Author: Eric Charles, 2011-03-16, 13:57
Sort:
project
HBase (38)
Impala (3)
Bigtop (2)
HDFS (2)
Accumulo (1)
Flume (1)
Hadoop (1)
MapReduce (1)
Pig (1)
type
mail # user (37)
source code (1)
date
last 7 days (0)
last 30 days (0)
last 90 days (3)
last 6 months (6)
last 9 months (37)
author
Alex Baranau (3)
Michael Segel (3)
lars hofhansl (3)
James Taylor (2)
Vladimir Rodionov (2)
Andrey Stepachev (1)
Bartosz M. Frak (1)
Chris Tarnas (1)
Cristofer Weber (1)
David Arthur (1)
Em (1)
Eric Charles (1)
Jean-Daniel Cryans (1)
Jean-Marc Spaggiari (1)
Kireet Reddy (1)