ctubbsii commented on issue #4055: URL: https://github.com/apache/accumulo/issues/4055#issuecomment-1862342040
This is not surprising, because MiniAccumuloClusterControl was written as a MiniAccumuloCluster implementation of the more generic ClusterControl that was intended to create an abstraction layer so that ITs could be written to run on an existing standalone cluster, or on mini, and be relatively agnostic to which they were run on. I believe at the time it was created, mini only used one server of each type, so some of the options that were added to support a larger standalone cluster (like using the hostname) were left unimplemented in the mini implementation, and don't really apply (since the hostname for all mini is effectively "localhost"). Most of our tests do not really use these features, and I do not know if the standalone capability works. I suspect it hasn't really worked since prior to 2.0, because that was the last time I remember anybody trying to use it. A lot of this is cruft that has stuck around as previous attempts to add features to our integration tests, but time consuming to rip out or polish up to simplify the ITs. In addition to the cluster control stuff, there is the AccumuloCluster interface, and the AccumuloClusterHarness/MiniClusterHarness, and the AccumuloITBase and its various subclasses, SharedMiniClusterBase and ConfigurableMacBase, that most of the ITs extend. Very few of them call any of the ClusterControl stuff at all. I would probably advocate for aggressive ripping out and simplifying, rather than trying to implement all the features of each of these framework classes. -- 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]
