[
https://issues.apache.org/jira/browse/ZOOKEEPER-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894282#comment-13894282
]
Raul Gutierrez Segales commented on ZOOKEEPER-1877:
---------------------------------------------------
And just to expand what [~cchen] described: the bad ACL causes the crash when
in the FinalRequestProcessor, so the request *will* be in the transaction log
and the cluster won't come back after the crashes.
> Malformed ACL Id can crash server with skipACL=yes
> --------------------------------------------------
>
> Key: ZOOKEEPER-1877
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1877
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.0
> Reporter: Chris Chen
> Attachments: ZOOKEEPER-1877.patch
>
>
> Because of the way fixupACL is written in PrepRequestProcessor, a request
> that feeds in an ACL with null members in the Id will cause a server with
> skipACL=yes to crash.
> A patch will be provided that re-introduces checks for well-formed ACLs even
> if skipACL is enabled.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
