[ https://issues.apache.org/jira/browse/HBASE-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455474#comment-13455474 ]
Lars Hofhansl commented on HBASE-3775: -------------------------------------- It seems this is no longer an issue. Agreed? > 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