[GitHub] [accumulo] ctubbsii commented on issue #2908: MiniAccumuloCluster binds admin.serverPort to 8080

[GitBox <gi...@apache.org>]

ctubbsii commented on issue #2908:
URL: https://github.com/apache/accumulo/issues/2908#issuecomment-1233544930

   Closing this as already addressed in the next release. See below for workarounds for previous releases.
   
   This only affects older Accumulo versions using a newer version of ZooKeeper that those Accumulo versions were not explicitly designed to work with. While newer versions of ZooKeeper should work with Accumulo 2.0 and 1.10, there may be some newer features in newer ZooKeeper releases that these versions of Accumulo do not explicitly support. Accumulo 1.10 and 2.0 were developed and tested primarily with ZooKeeper 3.4, which did not have an adminServer. The way we support arbitrary ZooKeeper configuration for mini is by providing the ability to use a ZooKeeper instance you start yourself.
   
   Mini itself does not use the adminServer and disables it in 2.1.0-SNAPSHOT (see #1531), so it's will not be an issue in that version, which will be the first version to be written explicitly to support ZooKeeper 3.5 and newer, after the adminServer was introduced.
   
   The workaround for this would be to use an existing ZooKeeper instance, which you can set up separately using whatever zoo.cfg you prefer. This is supported in the MiniAccumuloCluster API for Accumulo 1.10 and 2.0. You could use something like revelc/zookeeper-maven-plugin or start ZooKeeper yourself.
   
   Another workaround that ZooKeeper itself supports is: `System.setProperty("zookeeper.admin.enableServer", "false");`


-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org