You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

(warning) Work in Progress (warning)

Overview

The sequence diagrams below are intended to be a very detailed description of the interactions that occur during the process of defining, submitting and executing a map reduce job on a secure Hadoop 2.x cluster.

The descriptions of the interactions below take this form.

message [Protocol] ( input ) : output

The [Protocol] portion describes the protocol, authentication mechanism and identities exchanged.

Abbreviation

Description

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="75ffd496-3f8b-4f03-89cd-98d0902fa4ce"><ac:plain-text-body><![CDATA[

[KRB]

Kerberos Protocol

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e9553905-d682-45ee-944d-5f9f0c81c598"><ac:plain-text-body><![CDATA[

[RSK:{ticket}]

RPC protocol with SASL mutual authentication using Kerberos tickets.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d781dbfa-db13-4844-91d5-1d3953df25d9"><ac:plain-text-body><![CDATA[

[RST:{ticket}]

RPC protocol with SASL mutual authentication using delegation tokens.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3015b20d-d49f-477d-80d2-1f0bb18c8ce2"><ac:plain-text-body><![CDATA[

[RSD:{delegation-token}]

RPC protocol with SASL mutual authentication using delegation tokens.

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="09b0b27f-bf5d-4ec7-8af8-bf3ce1eeb78c"><ac:plain-text-body><![CDATA[

[DTP]

Data transfer protocol between the DataNode and a client. HTTP protocol with block tokens plus SHA1 hash exchange.

]]></ac:plain-text-body></ac:structured-macro>

Suffixes are used in many cases to denote type.

Abbreviation

Description

tgt

Kerberos Ticket Granting Ticket

kp

Kerberos Principal: nn-kp = The Kerberos principal for the NameNode nn

kt

Kerberos Ticket: u-jt-kt = A Kerberos Ticket for User u to access the JobTracker jt

sk

Secret Key

dt

Delegation Token

tkn

Token

Kerberos principals use the principal abbreviation and the kp suffix.

Abbreviation

Description

nn-kp

NameNode's Kerberos Principal

dn-kp

DataNode's Kerberos Principal (Unique principal for each DataNode on every node)

jt-kp

JobTracker's Kerberos Principal

tt-kp

TaskTracker's Kerberos Principal (Unique principal for each TaskTracker on every node)

Kerberos tickets use the consumer principal abbreviation, provider principal abbreviation and kt suffix.

Abbreviation

Description

u-nn-kt

Kerberos service ticket for User u to access NameNode nn

u-jt-kt

Kerberos service ticket for User u to access JobTracker jt

dn-nn-kt

Kerberos service ticket for DataNode dn to access NameNode nn

jt-nn-kt

Kerberos service ticket for JobTracker dn to access NameNode nn

tt-jt-kt

Kerberos service ticket for TaskTracker tt to access JobTracker jt


Secure MapReduce2 - Bootstrap


Secure MapReduce2 - Job Definition


Secure MapReduce2 - Job Submission


Secure MapReduce2 - Job Initiation


Secure MapReduce2 - Map Task Execution


Secure MapReduce2 - Reduce Task Execution


Secure MapReduce2 - Job Completion


Secure MapReduce2 - Client Monitoring

  • No labels