[ https://issues.apache.org/jira/browse/HBASE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557787#comment-13557787 ]
stack commented on HBASE-7533: ------------------------------ You would put RegionMovedException and DoNotRetryIOException together into a new Exception named RegionRelocationException? I don't follow how not retrying is related to Region Relocation. bq. ... We can designate a special value for RegionRelocationData.serverName which tells client that client should not retry. The above seems a little cryptic, don't you think? Unless I hear otherwise, I'll add a do not retry flag to our base stringified exception Message (might as well add ServerName to the base Message too -- c/c++s might be able to make sense of it). Will also add special case RegionMovedException pulling out the hostname and port whenever I see one of these... > Write an RPC Specification for 0.96 > ----------------------------------- > > Key: HBASE-7533 > URL: https://issues.apache.org/jira/browse/HBASE-7533 > Project: HBase > Issue Type: Bug > Reporter: stack > Assignee: stack > Fix For: 0.96.0 > > Attachments: 7533_proto_sketch.txt, rpc_spec.txt > > > RPC format is changing for 0.96 to accomodate our protobufing all around. > Here is a first cut. Please shred: > https://docs.google.com/document/d/1-1RJMLXzYldmHgKP7M7ynK6euRpucD03fZ603DlZfGI/edit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira