ddanielr commented on PR #5966: URL: https://github.com/apache/accumulo/pull/5966#issuecomment-3555085628
> > So we would define a range per component type per resource group. Not sure that we want/need that kind of fine grained control or if we just want ranges per component type regardless of RG. > > As mentioned, may be able to do this already in accumulo-env.sh using `-o`. Also, can this be accomplished by setting the prop at a RG level in zookeeper? We currently can't do this in accumulo-env.sh because all of the JAVA_OPTS are set before calling start.Main. So "-o" is interpreted by java as an invalid opt https://github.com/apache/accumulo/blob/b29f014253eb18ee4fe74f993c61badff713c9d6/assemble/bin/accumulo#L89 We used to support EXTRA_ARGS by `accumulo-cluster` https://github.com/apache/accumulo/blob/8f52dd10f7cbfef192c9cc431543619b7072139a/assemble/bin/accumulo-cluster#L166-L167 But that was removed in 2.1.4 ``` ./bin/accumulo-cluster start --tservers -o tserver.port.client=9954 accumulo-cluster: invalid option -- 'o' Usage: accumulo-cluster <command> [<option> ...] ``` @dlmarion is right, we would need to create another var that gets set on the end of the accumulo execute script. -- 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]
