[
https://issues.apache.org/jira/browse/ZOOKEEPER-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873664#comment-16873664
]
Fangmin Lv commented on ZOOKEEPER-3418:
---------------------------------------
Yes, that's the protocol change I mentioned, we need the leader/learner to
understand the error out case, which we don't have for now. Need to deal with
things like backward compatible, but it should be doable, what's your idea on
this?
> Improve quorum throughput through eager ACL checks of requests on local
> servers
> -------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3418
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3418
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.6.0
> Reporter: Michael Han
> Assignee: Michael Han
> Priority: Major
> Labels: Twitter, pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Serving write requests that change the state of the system requires quorum
> operations, and in some cases, the quorum operations can be avoided if the
> requests are doomed to fail. ACL check failure is such a case. To optimize
> for this case, we elevate the ACL check logic and perform eager ACL check on
> local server (where the requests are received), and fail fast, before sending
> the requests to leader.
> As with any features, there is a feature flag that can control this feature
> on, or off (default). This feature is also forward compatible in that for new
> any new Op code (and some existing Op code we did not explicit check
> against), they will pass the check and (potentially) fail on leader side,
> instead of being prematurely filtered out on local server.
> The end result is better throughput and stability of the quorum for certain
> workloads.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
