[
https://issues.apache.org/jira/browse/HBASE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553139#comment-13553139
]
Elliott Clark commented on HBASE-7533:
--------------------------------------
At this point a rogue client can pretty easily bring down a cluster, so I don't
think that adding the complexity of a rules based system on the server will
really buy us any resiliency. We could be sanity check the priority on the
server side.
bq.There could be a bunch of other factors that determine the priority
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.
Additionally having the ability to expose priority to the user would be really
useful feature that we would get for almost no extra cost. In my eyes that
would be a start towards allowing users to have mapred and realtime use cases
on the same hardware.
> 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
