arvindshmicrosoft commented on issue #1568: Support multiple tservers / node in accumulo-service URL: https://github.com/apache/accumulo/pull/1568#issuecomment-603590280 @ctubbsii I have redone this PR (hence the force push). Hopefully this version is more aligned with the guiding principles for the 2 scripts. One thing I'd like advice on (in addition to any other comments) is: given that accumulo-cluster currently does not source accumulo-env.sh, the user must export NUM_TSERVERS prior to invoking accumulo-cluster. This is probably fine for dev/test but I was hoping to define the variable somewhere on the node itself. Any thoughts on sourcing accumulo-env.sh in accumulo-cluster itself? I also observed in single-node testing (with Uno) with 2 TServers is that the user has to set gc.port.client to a number such as 10002 to avoid having GC pick port 9998 - which GC cannot - since 9998 has already been used by the second TServer running. So the second question I have is why do these scripts start TServers first, ahead of master, monitor and GC? I will try joining the Slack chat on Wednesday to discuss further if needed. Thank you and @keith-turner for working through this with me.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
