hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3775) Unique transient names for processes
Date Tue, 18 Sep 2012 21:54:08 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-3775.
--------------------------

    Resolution: Won't Fix

Marking as 'Wont Fix' with UUIDs.  I think hbase-1502 ServerName addresses Andrew's concern.
 Reopen Andrew if you see hole in my reasoning.
                
> Unique transient names for processes
> ------------------------------------
>
>                 Key: HBASE-3775
>                 URL: https://issues.apache.org/jira/browse/HBASE-3775
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Andrew Purtell
>
> HBASE-3772 is the latest of several incidents where regionservers and master map their
identities to hostnames yet hostname resolution is inconsistent cluster wide. With HBase 0.20
we have seen this lead conditions like META being hosted on 11 servers at once. The situation
with HBase 0.90 is better but it concerns me a lot. Confusion about identity cannot be anything
but bad.
> Why don't we have the processes generate for themselves a random UUID upon startup, or
similar, and have all processes on the cluster map these UUIDs to identities? Critically,
region assignment state should hold the UUID of the current assignee. This would not remove
the need to resolve region locations to network addresses, nor determine liveness of assignments,
but will prevent the specific double assignment scenarios we have seen if hostname resolution
is flaky.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message