[GitHub] [hadoop-ozone] linyiqun edited a comment on pull request #1454: HDDS-4285. Read is slow due to frequent calls to UGI.getCurrentUser() and getTokens()

[GitBox <gi...@apache.org>]

linyiqun edited a comment on pull request #1454:
URL: https://github.com/apache/hadoop-ozone/pull/1454#issuecomment-701381759


   >since it's a user token, suppose it has a much longer liveness than input and output stream object instance, right?
   
   A good point that @ChenSammi mentioned, there is a setting to decide the expired time of block token and it's a long time as 1 day. This should be an enough time for client to read/write block data. Suppose there also should be some service to renew expired token.
   
   ```xml
     <property>
       <name>hdds.block.token.expiry.time</name>
       <value>1d</value>
       <tag>OZONE, HDDS, SECURITY, TOKEN</tag>
       <description>
         Default value for expiry time of block token. This
         setting supports multiple time unit suffixes as described in
         dfs.heartbeat.interval. If no suffix is specified, then milliseconds is
         assumed.
       </description>
     </property>
   ```
   
   In additional, I'm +1 for current change. Thanks @adoroszlai  for addressing the comment.


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org