...
Code Block |
---|
message [Protocol] ( input ) : output |
The {{\ Wiki Markup [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="8526538f-243a-458b-a7b1-1f2bb46761df"><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="4361f040-91a0-47db-b298-41cfde58fdf0"><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="b2b662ac-da20-4bd6-a1d9-571c33433ade"><ac:plain-text-body><![CDATA[ |
| RPC protocol with SASL client authentication using access tokens (e.g. YARN Node Manager Token). ]]></ac:plain-text-body></ac:structured-macro> | <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="efc27897-1fe6-4e89-8392-3e8de2ec6de3"><ac:plain-text-body><![CDATA[ | ||
| RPC protocol with SASL client authentication using delegation tokens (e.g. HDFS Name Node Delegation Token). | ]]></ac:plain-text-body></ac:structured-macro> | <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5e502c09-4af0-42f7-a2a4-0e767a1c95a5"><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="705b9ef7-3911-44aa-a061-f567fb419479"><ac:plain-text-body><! | 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.
...
This diagram illustrates the steps taken by a Client to monitor the status of a Job throughout the Job's life-cycle. The timeframe for this diagram span several of the diagrams above starting from Job Submission all the way through Job Completion.
- TODO
- TODO
- TODO
...
NodeManager Token Flow
This diagram illustrates the flow of NodeManager Tokens throughout a MapReduce Job's life-cycle.
- TODO
- TODO
- TODO