[
https://issues.apache.org/jira/browse/HBASE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553174#comment-13553174
]
Devaraj Das commented on HBASE-7533:
------------------------------------
{quote}
At this point a rogue client can pretty easily bring down a cluster, so...
We could be sanity check the priority on the server side.
I don't think that we can anticipate all of the factors that users will want to
include. So it's easier to let users add their logic on the client side rather
than the server side.
{quote}
Fair points.. For now, let's make the priority an optional field in the RPC and
let the client send it. That would give us enough wiggle room to switch to an
alternate implementation (and at that point maybe make it configurable on
whether we would honor client's notion of priority..).
bq. I don't think that we can anticipate all of the factors that users will
want to include
Of course.. I meant to just give examples of other things that the server might
want to consider before assigning priority to a request...
> 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
>
>
> 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
