[YARN-3522] DistributedShell uses the wrong user to put timeline data

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.7.1, 3.0.0-alpha1
• Component/s: timelineserver
• Target Version/s: 2.7.1
• Hadoop Flags: Reviewed
• Assignee: Zhijie Shen
• Reporter: Zhijie Shen
• Created: 21/Apr/15 22:22
• Updated: 05/Jan/17 22:47
• Resolved: 23/Apr/15 18:08

Description

YARN-3287 breaks the timeline access control of distributed shell. In distributed shell AM:

    if (conf.getBoolean(YarnConfiguration.TIMELINE_SERVICE_ENABLED,
      YarnConfiguration.DEFAULT_TIMELINE_SERVICE_ENABLED)) {
      // Creating the Timeline Client
      timelineClient = TimelineClient.createTimelineClient();
      timelineClient.init(conf);
      timelineClient.start();
    } else {
      timelineClient = null;
      LOG.warn("Timeline service is not enabled");
    }

      ugi.doAs(new PrivilegedExceptionAction<TimelinePutResponse>() {
        @Override
        public TimelinePutResponse run() throws Exception {
          return timelineClient.putEntities(entity);
        }
      });

YARN-3287 changes the timeline client to get the right ugi at serviceInit, but DS AM still doesn't use submitter ugi to init timeline client, but use the ugi for each put entity call. It result in the wrong user of the put request.

Issue Links

• is broken by: YARN-3287 TimelineClient kerberos authentication failure uses wrong login context.