[jira] Commented: (HBASE-2052) Make hbase more 'live' when comes to noticing table creation, splits, etc., for 0.20.3

["dhruba borthakur (JIRA)" <ji...@apache.org>]

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

dhruba borthakur commented on HBASE-2052:
-----------------------------------------

Does this patch has any performance implication for large clusters?

It appears to me that when a region is split, the RegionServer has to inform the master. This occurs in the next heartbeat from the region server to the master. If so, can the regionserver send a immediate heartbeat message after a region split instead of waiting for the next  hbase.regionserver.msginteral to expire?




> Make hbase more 'live' when comes to noticing table creation, splits, etc., for 0.20.3
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-2052
>                 URL: https://issues.apache.org/jira/browse/HBASE-2052
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.20.3
>
>         Attachments: HBASE-2052.patch
>
>
> Clusters > 10 are less frequent that smaller clusters.  Defaults for when messages are sent from regionserver to master would seem to favor clusters that are much larger than ten nodes.  This issue is about changing them so the basic hbase setup is more live.  Its about downing the interval between RS sending messages from 3 to 1 second and of making clients retry more frequently at least at the start of the timeout period so they pick up changes the quicker.  This should help with stuff like noticing splits and new regions coming on line.  See HBASE-1892 for background.

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