[
https://issues.apache.org/jira/browse/HBASE-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798181#action_12798181
]
stack commented on HBASE-2052:
------------------------------
On large clusers, master would be doing more work when interval is low. The
interval should be upped on bigger clusters (Usual clusters sizes are 10-20
nodes that we hear of).
Yeah, if a regionserver has something to send the master, we've already made it
so that is sent immediately without waiting on the msg interval to expire but,
then once the message to split makes it to master, it won't assign until a
regionserver checks in (we're adding 'push' of messages in 0.21 using zk
watchers... master will add region to assign to a queue up in zk... this will
trigger a watcher on designated regionserver).
> 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.
