One, configure the history server
1. Configure the history server to configure the following in Etc/hadoop/mapred-site.xml.
<span style= "FONT-SIZE:18PX;" ><span style= "FONT-SIZE:18PX;" > <property> <name>mapreduce.jobhistory.address</name> <value>localhost :10020</value> </property> <property> <name> mapreduce.jobhistory.webapp.address</name> <value>localhost:19888</value> </ Property></span></span>
2. Distributing the configuration to all servers
3. Start the service to execute the following statement on this server on localhost:
mr-jobhistory-daemon.sh Start Historyserver
Two, configure Timeline server
1. Configure the history server to configure the following in Etc/hadoop/yarn-site.xml.
<span style= "FONT-SIZE:18PX;" ><!--Start Timeline Settings--<property> <description></description> <name>ya rn.timeline-service.hostname</name> <value>localhost</value> </property> <property> <description>address for the Timeline server to start the RPC server.</description> <name>yarn.timelin E-service.address</name> <value>${yarn.timeline-service.hostname}:10200</value></property ><property> <description>the http Address of the Timeline service Web application.</description> &L T;name>yarn.timeline-service.webapp.address</name> <value>${yarn.timeline-service.hostname}:8188 </value></property><property> <description>the HTTPS address of the Timeline service web Application.</description> <name>yarn.timeline-service.webapp.https.address</name> <value >${yarn.timeline-service.hostnaMe}:8190</value></property><property> <description>handler thread count to serve the client RPC requests.</description> <name>yarn.timeline-service.handler-thread-count</name> <value >10</value></property><property> <description>enables cross-origin Support (CORS) for web Services where Cross-origin Web response headers is needed. For example, JavaScript making a Web services request to the timeline server.</description> <name>yarn.timel Ine-service.http-cross-origin.enabled</name> <value>false</value></property>< Property> <description>comma separated list of origins that is allowed for Web services needing cross-origin ( CORS) support. Wildcards (*) and Patterns allowed</description> <name> Yarn.timeline-service.http-cross-origin.allowed-origins</name> <value>*</value></property ><property> <description>comma Separated list of methods that is allowed for Web services needing cross-origin (CORS) support.</description> &L T;name>yarn.timeline-service.http-cross-origin.allowed-methods</name> <value>GET,POST,HEAD</ Value></property><property> <description>comma separated list of headers that is allowed for Web s Ervices needing cross-origin (CORS) support.</description> <name> Yarn.timeline-service.http-cross-origin.allowed-headers</name> <value>x-requested-with,content-type ,accept,origin</value></property><property> <description>the number of seconds a Pre-flighted request can be cached for Web services needing cross-origin (CORS) support.</description> <name> ;yarn.timeline-service.http-cross-origin.max-age</name> <value>1800</value></property> <property> <description>indicate to ResourceManager as well as clients whether History-service are EnabLED or not. If enabled, ResourceManager starts recording historical data that Timelien service can consume. Similarly, clients can redirect to the "History service" when applications finish if it is enabled.</description> <name>yarn.timeline-service.generic-application-history.enabled</name> <value>true</value ></property><property> <description>store class name for the history Store, defaulting to file system s Tore</description> <name>yarn.timeline-service.generic-application-history.store-class</name> <value>org.apache.hadoop.yarn.server.applicationhistoryservice.filesystemapplicationhistorystore</ Value></property><property> <description>indicate to clients whether Timeline service is enabled Or not. If enabled, the Timelineclient library used by end-users would post entities and events to the Timeline SERVER.</DESCRI Ption> <name>yarn.timeline-service.enabled</name> <value>true</value></property><property> <description>store class name for timeline Store.</description> <name>yarn.timeline-service.store-class</name> <value> Org.apache.hadoop.yarn.server.timeline.leveldbtimelinestore</value></property><property> < Description>enable age off of timeline store data.</description> <name> Yarn.timeline-service.ttl-enable</name> <value>true</value></property><property> <description>time to live for timeline store data in milliseconds.</description> <name> Yarn.timeline-service.ttl-ms</name> <value>6048000000</value></property> <!--end Timeline Settings--></span>
2. Distributing the configuration to all servers
3. Start the service to execute the following statement on this server on localhost:
yarn-daemon.sh Start Historyserver
Hadoop configuration History Server and Timeline server