elek commented on pull request #1562: URL: https://github.com/apache/ozone/pull/1562#issuecomment-773801642
> If changing the RPC transport requires implementing a new client then it could become a significant task. The proposal suggested using the same OzoneClient as before, the only new part is a new `org.apache.hadoop.ozone.om.protocolPB.OmTransportFactory` implementation. > We have also talked about decoupling S3 users from Kerberos IMHO it's an independent question. At least if we are talking about the client usage. That requires a change on OM side to create the secret on a different way. It's independent of the internal communication between OM S3G. This change can make it possible to start s3g without kerberos, It makes it possible to start stateless s3g services side-by-side with S3 clients. And I believe using Hadoop RPC in this case has more limitations. This is a very specific case use, and caching and authentication of Hadoop RPC are implemented for per-request, client use case. For example the caching is hard-coded, using static fields. ---------------------------------------------------------------- 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: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
