hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vamshi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4137) Implementation of Distributed Hash Table(DHT) for lookup service
Date Wed, 27 Jul 2011 10:15:09 GMT

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

vamshi commented on HBASE-4137:

Hi stack, i thought in some different manner and i posted that description. i had a different
view then.i'll change it once i get a clear perspective  from the below queries..    

I have small doubt regarding Root and .META. Actually where the Root and .META. are stored
in the HBase cluster? Are they stored in two different special machines in which no other
regions stored? 
One more thing is, is Root and  .META. distributed or they are fully present in a single system
(same or different systems)?  
If Root is present on a single system and if there are somany requests from clents(for first
time) which is obvious in real time environment, it might be a bottle neck for Root .In that
case to get rid-off the Root from that problem, can we distribute the Root? And can we use
DHT(Distributed Hash table) then, for load balancing of requests?  
please give me a clarity on it..so that i can move ahead.   Thank you stack..

> Implementation of Distributed Hash Table(DHT)  for lookup service
> -----------------------------------------------------------------
>                 Key: HBASE-4137
>                 URL: https://issues.apache.org/jira/browse/HBASE-4137
>             Project: HBase
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 0.90.3
>            Reporter: vamshi
> To implement  a scalable data structure i.e Distributed hash table in the HBase. In the
Hbase to perform fast lookup  we can take the help of Distributed Hash Table (DHT), a scalable
data structure.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message