You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/05/31 17:57:04 UTC

[jira] [Commented] (HBASE-18134) Re-think if the FileSystemUtilizationChore is still necessary

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

Josh Elser commented on HBASE-18134:
------------------------------------

Re-reading my notes and found an important detail I missed. The thought process is that, after a Region is opened by a RegionServer, all other code paths which will change that Region's size on HDFS would be covered by HBASE-18133.

So, instead of having a chore to periodically read+queue-for-send size reports for Regions, we just queue a size report after the Region is opened. I believe this completely eliminates the need for the FileSystemUtilizationChore. 

> Re-think if the FileSystemUtilizationChore is still necessary
> -------------------------------------------------------------
>
>                 Key: HBASE-18134
>                 URL: https://issues.apache.org/jira/browse/HBASE-18134
>             Project: HBase
>          Issue Type: Task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>
> On the heels of HBASE-18133, we need to put some thought into whether or not there are cases in which the RegionServer should still report sizes directly from HDFS.
> The cases I have in mind are primarily in the face of RS failure/restart. Ideally, we could get rid of this chore completely.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)