[GitHub] [hadoop] symious commented on pull request #3579: HADOOP-17975 Fallback to simple auth does not work for a secondary DistributedFileSystem instance.

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

symious commented on pull request #3579:
URL: https://github.com/apache/hadoop/pull/3579#issuecomment-958605853


   @fapifta Thanks for the explanation. 
   
   Is the current situation as follows? Correct me if I'm wrong. 
   
   Server S has two clients, client A of non-secure settings with "fallbackToSimpleAuth = false", client B of secure settings with "fallbackToSimpleAuth=true", client A and B both connecting to Datanode D, since client A first connect to Datanode D, so the connection is created in _connections_, and the fallbackToSimpleAuth is set to false.
   Then client B tries to connect Datanode D, since the _ConnectionId_ is the same, it will reuse the connection created by Client A, then in _setupIOStream_, since the socket is created, Client will skip the other process, and the "fallbackToSimpleAuth" won't be changed to true.
   
   If the issue is caused by the above situation, I think if we distinguish the connections of Client A and Client B will solve the issue? Currently the ConnectionId of Client A and Client B is same, if we add "fallbackToSimpleAuth" to ConnectionId, since Client A has "false" and Client B has "true", they will generate different ConnectionId, then different connections will be created, so they won't affect each other.


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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



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