hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12853) distributed write pattern to replace ad hoc 'salting'
Date Thu, 30 Jul 2015 19:32:04 GMT

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

Andrew Purtell commented on HBASE-12853:
----------------------------------------

bq.  Either you find value to the suggestion or not. That is your call. But please note that
Andrew P. worked on https://issues.apache.org/jira/browse/HBASE-13044. (Also relatively trivial)

Not sure I understand the relevance. For the record, I filed that issue after a brief encounter
with Jim Scott of MapR over on the OpenTSDB list. He spoke of customers implementing coprocessors
that exist solely to prevent loading of any other coprocessors, so I thought we could do something
simple to make that unnecessary and volunteered time to do it. Strictly speaking, I didn't
have to but the conversation was respectful and interesting and I felt like volunteering some
of my evening that evening rather than spend it with family.

The committer role at Apache is not about requiring individuals to implement unfunded mandates
from random folks. On the other hand, we are expected to try and assess all contributions
in the form of a patch in the most impartial manner possible. If for whatever reason you are
not in a position to provide a patch, that's fine, but understand you are speaking to a community
of volunteers who have work and personal lives and are already being super generous just for
showing up here from time to time. You'll have to find a way to convince them they should
volunteer their time to help you. Sometimes under the best of circumstances that just won't
happen. An abrasive communication style - for example, repeated comments about "lack[ing]
the patience to suffer fools" - dooms you to failure out of the gate. Don't be surprised at
your lack of results.

> distributed write pattern to replace ad hoc 'salting'
> -----------------------------------------------------
>
>                 Key: HBASE-12853
>                 URL: https://issues.apache.org/jira/browse/HBASE-12853
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Michael Segel 
>             Fix For: 2.0.0
>
>
> In reviewing HBASE-11682 (Description of Hot Spotting), one of the issues is that while
'salting' alleviated  regional hot spotting, it increased the complexity required to utilize
the data.  
> Through the use of coprocessors, it should be possible to offer a method which distributes
the data on write across the cluster and then manages reading the data returning a sort ordered
result set, abstracting the underlying process. 
> On table creation, a flag is set to indicate that this is a parallel table. 
> On insert in to the table, if the flag is set to true then a prefix is added to the key.
 e.g. <region server#>- or <region server #|| where the region server # is an integer
between 1 and the number of region servers defined.  
> On read (scan) for each region server defined, a separate scan is created adding the
prefix. Since each scan will be in sort order, its possible to strip the prefix and return
the lowest value key from each of the subsets. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message