hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7948) client doesn't need to refresh meta while the region is opening
Date Wed, 27 Feb 2013 02:41:11 GMT

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

Enis Soztutar commented on HBASE-7948:

Overall looks good. Some comments:
 - We probably don't want the conf/log4j.properties (and the other one under hbase-server/src/test)
change for TRACE logging. 
 - not sure why this import is there in hbase-client/src/main/java/org/apache/hadoop/hbase/exceptions/NotServingRegionException.java

 +import org.apache.hadoop.ipc.RemoteException;
 - I think if we cache RS that it is OPENING, and RS fails to do so, we will go to RS again,
then get a NotServingException, and refetch meta again, right. Just asking to confirm that
we do not have to wait the grace period. 
 - Since RS only updates meta with location after it opens the region, this is only useful
when combined with RegionMovedException's, right? 
> client doesn't need to refresh meta while the region is opening
> ---------------------------------------------------------------
>                 Key: HBASE-7948
>                 URL: https://issues.apache.org/jira/browse/HBASE-7948
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HBASE-7948-v0.patch

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

View raw message