bharatviswa504 edited a comment on pull request #1149: URL: https://github.com/apache/hadoop-ozone/pull/1149#issuecomment-665199438
> Yesterday we got a question on ASF slack the OM (port=9874) couldn't be accessible AWS cli. The answers is simple (for us): we need separated s3g process and 9878 should be used. > > But it seems to be hard to communicate the details of our design. Making something work out-of-the box (without requiring additional configuration like internal service.id) seems to have a huge benefit. I get that point. My suggestion is if service.id is set and having only one value, we can use this value, without users trying to pass service id for the shell. But when someone tries to add more service ids and make their old commands work, they can set internal.service.id. (I agree that by default setting internal.service.id is not required for shell commands). I am fine as it does not affect FS. I have one question, Suppose I have a configuration, like ozone.om.address and ozone.om.service.id value set, still we pick ozone.om.service.id here. But let's say my intention was to talk to non-HA cluster. I know I am coming with some peculiar scenarios. But guessing everything without user passing info can cause these kinds of issues. (Previously we used to throw an error, now we talk to remote HA cluster and perform operations) ---------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
