YARN-3516. killing ContainerLocalizer action doesn't take effect when
private localizer receives FETCH_FAILURE status. Contributed by zhihai
xu
(cherry picked from commit 0b3f8957a8
)
This commit is contained in:
parent
f27a976a2f
commit
8f6053ae51
|
@ -209,6 +209,9 @@ Release 2.8.0 - UNRELEASED
|
|||
YARN-3434. Interaction between reservations and userlimit can result in
|
||||
significant ULF violation (tgraves)
|
||||
|
||||
YARN-3516. killing ContainerLocalizer action doesn't take effect when
|
||||
private localizer receives FETCH_FAILURE status.(zhihai xu via xgong)
|
||||
|
||||
Release 2.7.1 - UNRELEASED
|
||||
|
||||
INCOMPATIBLE CHANGES
|
||||
|
|
|
@ -989,7 +989,7 @@ public class ResourceLocalizationService extends CompositeService
|
|||
case FETCH_FAILURE:
|
||||
final String diagnostics = stat.getException().toString();
|
||||
LOG.warn(req + " failed: " + diagnostics);
|
||||
response.setLocalizerAction(LocalizerAction.DIE);
|
||||
action = LocalizerAction.DIE;
|
||||
getLocalResourcesTracker(req.getVisibility(), user, applicationId)
|
||||
.handle(new ResourceFailedLocalizationEvent(
|
||||
req, diagnostics));
|
||||
|
|
Loading…
Reference in New Issue