You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "stack (JIRA)" <ji...@apache.org> on 2007/09/26 07:28:51 UTC

[jira] Updated: (HADOOP-1928) [hbase] Have master pass the regionserver the filesystem to use

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

stack updated HADOOP-1928:
--------------------------

    Attachment: master_passing_config.patch

Here's a first cut.  Lots of HRegionServer refactoring so no fs access nor service thread startups until after we've had our first conversation with master.  Needs testing on a cluster.

> [hbase] Have master pass the regionserver the filesystem to use
> ---------------------------------------------------------------
>
>                 Key: HADOOP-1928
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1928
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>         Attachments: master_passing_config.patch
>
>
> The less configuration needed starting a regionserver the better.  Currently the regionserver needs to read hadoop-site mainly so it knows which filesystem to go against.  If it could get this info from the master instead when it gets the response to its reporting-for-duty message, then the dependency on hadoop-site.xml could mostly go away.
> Looking at regionserver, it looks like it would just take a little reorganization so that the hlog opening and the startup of worker threads doesn't happen until after we get our first response from the master.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.