[
https://issues.apache.org/jira/browse/HBASE-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-2190:
-------------------------
Attachment: 2190-v3.patch
Messages on RS are now on a hair-trigger; as soon as one available, its passed
the master. All seems snappier -- splitting and table creation. I think this
will help with table enable/disable type stuff too. We'll see. Still testing
it up on cluster to make sure no message duplication, etc.
Here are some commit notes for attached patch:
{code}
M src/test/org/apache/hadoop/hbase/TestHMsg.java
Add serialization tests.
M src/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
Changed outboundMsgs from array to LinkedBlockingQueue.
Moved housekeeping AFTER pause since when before, its addition of
"processing open" would make it so we didn't sleep and we were
flooding the master with "processing open" messages (this new mechanism
is on a hair-trigger).
Use new MSG_REPORT_SPLIT_WITH_DAUGHTERS HMsg which bundles up three
HMsgs as one.
Removed all synchronization on this.outboundMsgs. Seems unnecessary.
M src/java/org/apache/hadoop/hbase/master/ServerManager.java
Added handling of new MSG_REPORT_SPLIT_WITH_DAUGHTERS message.
M src/java/org/apache/hadoop/hbase/HMsg.java
Added new MSG_REPORT_SPLIT_WITH_DAUGHTERS message. Carries split
daughters as payload rather than send them as new individual messages.
Should be self-migrating. Will need to restart master first though
when doing a rolling-restart.
{code}
> HRS should report to master when HMsg are available
> ---------------------------------------------------
>
> Key: HBASE-2190
> URL: https://issues.apache.org/jira/browse/HBASE-2190
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.3
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.20.4, 0.21.0
>
> Attachments: 2190-v2.patch, 2190-v3.patch, HBASE-2190.patch
>
>
> It still takes a lot of time for the client to see splits or just regions
> that move around, with default PE it takes around 4 seconds and creating a
> table takes a bit more than 2 seconds. I remember having the discussion with
> Stack that HRS.run was not suppose to sleep if any message to send.
> Turns out it does sleep.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
