elek commented on pull request #1149:
URL: https://github.com/apache/hadoop-ozone/pull/1149#issuecomment-670847382


   > I think we reach consensus "convenience" should not be priority when 
multiple service ids are added even though they may have only one before. User 
must specify service id explicitly in that case.
   
   Based on my understanding we agreed to require explicit serviceId in 
`o3fs/ofs` and make it optional (if one is defined) for `OzoneClient`/API calls.
   
   API calls are used from other servers and CLI tools (both are related to 
admin use-cases and not related to user activities).
   
   The original argument against making `serviceId` optional if it can be 
deducted was the following:
   
   If It's optional in ofs/o3fs url, the url might need modification (make 
explicit from implicit) when additional HA services are used. Which makes it 
harder for Hive users to add secondary Ozone HA cluster.
   
   It seemed to be a particular use case, but I accepted this argument. Overall 
it's a decision between to forces:
   
    1. Make the system safer for Hive users who add additional Ozone HA cluster 
in the future, but slightly harder for new adopters
    2. Make the usability better for new adopters which adds additional risk 
for Hive users who add additional Ozone HA cluster in the future
   
   @arp7 and @bharatviswa504 argued that 1 is more important, and I accepted it.
   
   But as far as I understood we agreed that we make this improvement on API 
level (`OzoneClient`, `ozone sh`), which also means that S3 can be started 
easily. The original arguments are not applied to these cases, but I am open to 
discuss any additional problems, if you see...
   
   
   
   
   


----------------------------------------------------------------
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

Reply via email to