Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.6.0
-
None
-
Reviewed
-
Description
The ShellBasedUnixGroupsMapping run various id commands via the ShellCommandExecutor modules without a timeout set (its set to 0, which implies infinite).
If this command hangs for a long time on the OS end due to an unresponsive groups backend or other reasons, it also blocks the handlers that use it on the NameNode (or other services that use this class). That inadvertently causes odd timeout troubles on the client end where its forced to retry (only to likely run into such hangs again with every attempt until at least one command returns).
It would be helpful to have a finite command timeout after which we may give up on the command and return the result equivalent of no groups found.
Attachments
Attachments
Issue Links
- breaks
-
HADOOP-15523 Shell command timeout given is in seconds whereas it is taken as millisec while scheduling
- Resolved
- links to