hadoop 配置history server 和timeline server

一,配置history server

1.配置history server,在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.把配置分发到所有服务器

3.启动服务,以localhost这台服务器上执行以下语句:

mr-jobhistory-daemon.sh  start historyserver

二 ,配置timeline server

1.配置history server,在etc/hadoop/yarn-site.xml中配置以下内容.

<span style="font-size:18px;"><!--start timeline settings -->
  <property>
      <description></description>
    <name>yarn.timeline-service.hostname</name>
    <value>localhost</value>
  </property>
  <property>
  <description>Address for the Timeline server to start the RPC server.</description>
  <name>yarn.timeline-service.address</name>
  <value>${yarn.timeline-service.hostname}:10200</value>
</property>

<property>
  <description>The http address of the Timeline service web application.</description>
  <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 are needed. For example, javascript making
  a web services request to the timeline server.</description>
  <name>yarn.timeline-service.http-cross-origin.enabled</name>
  <value>false</value>
</property>

<property>
  <description>Comma separated list of origins that are 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 are allowed for web
  services needing cross-origin (CORS) support.</description>
  <name>yarn.timeline-service.http-cross-origin.allowed-methods</name>
  <value>GET,POST,HEAD</value>
</property>

<property>
  <description>Comma separated list of headers that are allowed for web
  services 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 is 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 this is enabled.</description>
  <name>yarn.timeline-service.generic-application-history.enabled</name>
  <value>true</value>
</property>

<property>
  <description>Store class name for history store, defaulting to file system
  store</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 will post entities
  and events to the Timeline server.</description>
  <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.把配置分发到所有服务器

3.启动服务,以localhost这台服务器上执行以下语句:

yarn-daemon.sh start historyserver

时间: 2024-11-08 23:09:46

hadoop 配置history server 和timeline server的相关文章

Hadoop HA HDFS启动错误之org.apache.hadoop.ipc.Client: Retrying connect to server问题解决

近日,在搭建Hadoop HA QJM集群的时候,出现一个问题,如本文标题. 网上有很多HA的博文,其实比较好的博文就是官方文档,讲的已经非常详细.所以,HA的搭建这里不再赘述. 本文就想给出一篇org.apache.hadoop.ipc.Client: Retrying connect to server错误的解决的方法. 因为在搜索引擎中输入了错误问题,没有找到一篇解决问题的.这里写一篇备忘,也可以给出现同样问题的朋友一个提示. 一.问题描述 HA按照规划配置好,启动后,NameNode不能

application master 持续org.apache.hadoop.ipc.Client: Retrying connect to server

一.问题现象 某一个nodemanager退出后,导致 application master中出现大量的如下日志,并且持续很长时间,application master才成功退出. 2016-06-24 09:32:35,596 INFO [ContainerLauncher #3] org.apache.hadoop.ipc.Client: Retrying connect to server: dchadoop206/192.168.1.199:32951. Already tried 1 

对Hadoop2.7.2文档的学习-Yarn部分(3)RM Restart/RM HA/Timeline Server/NM Restart

ResourceManger Restart ResourceManager负责资源管理和应用的调度,是YARN的核心组件,有可能存在单点失败的问题.ResourceManager Restart是使RM在重启动时能够使Yarn集群正常工作的feature,并且使RM的出现的失败不被用户知道. ResourceManager Restart feature is divided into two phases: ResourceManager Restart Phase 1 (Non-work-

hive与timeline server

timeline server挂了 hive也挂了 hive使用的tez 而tez设置了 Using YARN Timeline with Tez for History 详见http://tez.apache.org/tez_yarn_timeline.html 原文地址:https://www.cnblogs.com/roger888/p/11422539.html

配置PL/SQL Developer连接server数据库

配置PL/SQL Developer连接server数据库 远程应用server上安装client客户端软件,可在oracle官网上下载. 举例: 环境 应用server操作系统 WIN 7 本地地址 192.168.56.117 生产server操作系统 Enterprise Linux Server release 5.4 主机名 org54 主机地址 192.168.56.5 数据库版本号 Oracle Database 10g 数据库实例名 GAME client软件版本号 10201_

SQL Server 2008 /SQL Server 2008 R2 配置数据库邮件

原文:SQL Server 2008 /SQL Server 2008 R2 配置数据库邮件 从2005开始,就引入了"数据库邮件"功能.并且取代SQLMail.原有SQLMail可以继续使用. SQLMail要求有应用程序编程接口(Extended Messaging Application Programming Interface,MAPI),安装新的Office时可能导致SQLMail失败. 数据库邮件更加安全.可靠,并且不需要MAPI.具有群集感知能力.可以自动重传发送失败的

CentOS6.X下安装配置独立SVN服务器|Subversion server

Hi 大家好,我是钟义林,今天我们来安装一个Subversion服务吧,Subversion server其实就我们日常说的SVN服务,Subversion(简称SVN,svn),一个开放源代码的版本控制系统,相较于RCS.CVS,它采用了分支管理系统,它的设计目标就是取代CVS.互联网上很多版本控***务已从CVS转移到Subversion.svn服务器有2种运行方式:独立服务器和借助apache运行.下面我安装独立SVN 首先,清除一下yum的缓存吧,yum clean  all [一]安装

nginx配置默认80端口默认server

直接访问ip地址80端口,nginx解析到对应服务器 需要配置server default 参数 server {         listen       80     default;         server_name  www.mysite.com;         access_log  logs/qb.app.access.log  main;         error_log  logs/qb.app.error.log  warn;    }

CS8: 客户遇到多台Server 2008 或者Server 2008R2 服务器网关无故丢失配置

客户问题概括: 很多客户反馈某些Server会无规律丢失网关配置,造成网络中断,需要找到根本原因. 解决方法:经过多个系统日志分析发现网关配置丢失都是在服务器重启后发生,研究讨论后发现,Server 2008 或者Server 2008R2 在某些虚拟化环境下较多发丢失网关配置如(Vmware Esxi). 上述问题通过手动编辑(或新建)网卡默认网关注册表项即可解决,如下图,编辑或者新建对应网卡(注册表中叫Interfaces)的DefaultGateway 即可解决, 编辑完需要重启服务器才能