[
https://issues.apache.org/jira/browse/HBASE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-504:
------------------------
Attachment: 504-v3.patch
Here is a patch that adds optional messages. I added messages for split,
failing close (adds exception on why we're failing), and to the close if we're
closing because of the rebalancing.
Here is commit message:
{code}
M src/test/org/apache/hadoop/hbase/TestSerialization.java
Add test that HMsg with region and message serializes.
M src/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
HMsg types have been enumified. Also use some of the new
static messages. On split and close because of error,
add message to the HMsg we pass back to the master.
M src/java/org/apache/hadoop/hbase/HServerInfo.java
(compareTo): Added.
M src/java/org/apache/hadoop/hbase/HRegionInfo.java
Allow null in compareTo.
M src/java/org/apache/hadoop/hbase/master/ServerManager.java
Use the new HMsg.isType figuring message type.
Redo message logging. Use convenience HMsg statics.
M src/java/org/apache/hadoop/hbase/master/RegionManager.java
Pass back overloaded message if region shutdown because of balancing.
M src/java/org/apache/hadoop/hbase/HServerAddress.java
Make it so that two addresses equate even if one has hostname
and the other IP.
M src/java/org/apache/hadoop/hbase/ipc/HMasterRegionInterface.java
Up the protocol version for regionserver reporting master messages.
M src/java/org/apache/hadoop/hbase/HMsg.java
Enumify the messge types.
Define a few static HMsgs for convenience.
Allow optional message. Improved toString.
(isType, equals, hashCode): Added.
{code}
> Allow HMsg's carry a payload: e.g. exception that happened over on the remote
> side.
> -----------------------------------------------------------------------------------
>
> Key: HBASE-504
> URL: https://issues.apache.org/jira/browse/HBASE-504
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.16.0, 0.2.0, 0.1.0
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments: 504-v3.patch, message-v2.patch, ott.patch
>
>
> Will make it so can just look in master log and get a general sense of
> failure types, etc., across the cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
