Work in Progress
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. Different phases of the overall process are covered in each diagram.
- Bootstrap
- Job Definition
- Job Submission
- Job Initiation
- Map Task Execution
- Reduce Task Execution
- Job Completion
- Client Monitoring
Legend
The descriptions of the interactions in the sequence diagrams 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="0f1c4359-14d3-45de-af64-b30cf6d09269"><ac:plain-text-body><![CDATA[ |
|
Kerberos Protocol |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9bb070ab-bdeb-4e3d-b8c9-579ba321b230"><ac:plain-text-body><![CDATA[ |
|
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="c8fa66dd-8fc4-4fe4-844b-3752b28e386c"><ac:plain-text-body><![CDATA[ |
|
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="9e1c8739-e371-4f86-87bf-eee392b534f9"><ac:plain-text-body><![CDATA[ |
|
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="8881b448-dfbc-4d19-9da0-26fa5a9185cf"><ac:plain-text-body><![CDATA[ |
|
Shuffle data transfer protocol between ShuffleService and ReduceTask. HTTP protocol with TODO. |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="08ff2136-822c-4df1-88a6-db31e098c68b"><ac:plain-text-body><![CDATA[ |
|
Block 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 |
kt |
Kerberos Service Ticket: u-jt-kt = A Kerberos Ticket for User u to access the JobTracker jt |
kp |
Kerberos Principal: nn-kp = The Kerberos principal for the NameNode nn |
dt |
Delegation Token: c-nn-dt = A delegation token for identity of the Client that can be presented to the NameNode. |
tkn |
Access Token: am-tkn = An access token that can be presented to the ApplicationMaster for access. |
tkn-sk |
Token Secret Key |
Kerberos principals use the principal abbreviation and the kp suffix.
Abbreviation |
Description |
---|---|
|
NameNode's Kerberos Principal |
|
DataNode's Kerberos Principal (Unique principal for each DataNode on every node) |
|
JobTracker's Kerberos Principal |
|
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 |
---|---|
|
Kerberos service ticket for User u to access NameNode nn |
|
Kerberos service ticket for User u to access JobTracker jt |
|
Kerberos service ticket for DataNode dn to access NameNode nn |
|
Kerberos service ticket for JobTracker dn to access NameNode nn |
|
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