dlmarion commented on code in PR #371: URL: https://github.com/apache/accumulo-website/pull/371#discussion_r1094479917
########## _docs-2/troubleshooting/zookeeper.md: ########## @@ -3,6 +3,34 @@ title: ZooKeeper category: troubleshooting order: 7 --- +## ZooKeeper ACLs + +Accumulo requires full access to nodes in ZooKeeper under the /accumulo path. The ACLs can be examined using the +ZooKeeper cli `getAcl` and modified with `setAcl` commands. With 2.1.1, the zoo-info-viewer utility has an option +that will print all of the ACLs for the nodes under `/accumulo/[INSTANCE_ID]` (See the [zoo-info-viewer]). +To run the utility, only ZooKeeper needs to be running. If hdfs is running, the instance id can be read from hdfs, +or it can be entered with the zoo-info-viewer command --instanceId option. Accumulo management processes +*do not* need to be running. This allows checking the ACLs before starting an upgrade. + Review Comment: Might be useful to include a one or two line example output. ########## _docs-2/troubleshooting/zookeeper.md: ########## @@ -3,6 +3,34 @@ title: ZooKeeper category: troubleshooting order: 7 --- +## ZooKeeper ACLs + +Accumulo requires full access to nodes in ZooKeeper under the /accumulo path. The ACLs can be examined using the +ZooKeeper cli `getAcl` and modified with `setAcl` commands. With 2.1.1, the zoo-info-viewer utility has an option +that will print all of the ACLs for the nodes under `/accumulo/[INSTANCE_ID]` (See the [zoo-info-viewer]). +To run the utility, only ZooKeeper needs to be running. If hdfs is running, the instance id can be read from hdfs, +or it can be entered with the zoo-info-viewer command --instanceId option. Accumulo management processes +*do not* need to be running. This allows checking the ACLs before starting an upgrade. + +The utility prints out two summarized fields related to ZooKeeper ACL permissions: Review Comment: ```suggestion The utility prints out a line for each znode that contains two fields related to ZooKeeper ACL permissions: ``` ########## _docs-2/troubleshooting/zookeeper.md: ########## @@ -3,6 +3,34 @@ title: ZooKeeper category: troubleshooting order: 7 --- +## ZooKeeper ACLs + +Accumulo requires full access to nodes in ZooKeeper under the /accumulo path. The ACLs can be examined using the +ZooKeeper cli `getAcl` and modified with `setAcl` commands. With 2.1.1, the zoo-info-viewer utility has an option +that will print all of the ACLs for the nodes under `/accumulo/[INSTANCE_ID]` (See the [zoo-info-viewer]). +To run the utility, only ZooKeeper needs to be running. If hdfs is running, the instance id can be read from hdfs, +or it can be entered with the zoo-info-viewer command --instanceId option. Accumulo management processes +*do not* need to be running. This allows checking the ACLs before starting an upgrade. + +The utility prints out two summarized fields related to ZooKeeper ACL permissions: + - `[ACCUMULO_OKAY | ERROR_ACCUMULO_MISSING_SOME]` - Are the permissions sufficient for Accumulo to operate + - `[PRIVATE | NOT_PRIVATE]` - Can other users can read data from the ZooKeeper nodes. + +If there are nodes with `ERROR_ACCUMULO_MISSING_SOME` are nodes where Accumulo does not have `cdrwa` permissions. Review Comment: ```suggestion Nodes marked with `ERROR_ACCUMULO_MISSING_SOME` means that Accumulo does not have `cdrwa` permissions. ``` ########## _docs-2/troubleshooting/zookeeper.md: ########## @@ -3,6 +3,34 @@ title: ZooKeeper category: troubleshooting order: 7 --- +## ZooKeeper ACLs + +Accumulo requires full access to nodes in ZooKeeper under the /accumulo path. The ACLs can be examined using the +ZooKeeper cli `getAcl` and modified with `setAcl` commands. With 2.1.1, the zoo-info-viewer utility has an option +that will print all of the ACLs for the nodes under `/accumulo/[INSTANCE_ID]` (See the [zoo-info-viewer]). Review Comment: ```suggestion that will print all of the ACLs for the nodes under `/accumulo/[INSTANCE_ID]` (See [zoo-info-viewer]). ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
